From 6c490f6ae2ad7de477e3bfcbba9a037142df15ea Mon Sep 17 00:00:00 2001 From: Danilo Delizia Date: Tue, 6 Feb 2024 17:24:14 +0100 Subject: [PATCH] feat(security): securying endpoints with jwt and oauth2 --- processor/README.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/processor/README.md b/processor/README.md index d399d3d..9cc8253 100644 --- a/processor/README.md +++ b/processor/README.md @@ -33,9 +33,9 @@ Some of the services have authentication mechanism. * `session`: Relies on commercetools session service * `oauth2`: Relies on commercetools oauth2 server -While `session` and `oauth2` authentication mechanisms are easy to work locally, `jwt` will +While `session` and `oauth2` authentication mechanisms are easy to work locally, `jwt` will need some workaround to be able to test locally as depends on the merchant center forward-to proxy. -In order to make easy running the application locally, the code comes with a jwt mock server +In order to make easy running the application locally, the code comes with a jwt mock server: ``` # Set environment variable to point to the jwksUrl @@ -59,4 +59,4 @@ curl --location 'http://localhost:9000/jwt/token' \ {"token":""} ``` -Use the token to authenticate your requests. \ No newline at end of file +Use the token to authenticate requests protected by JWT: `Authorization: Bearer `. \ No newline at end of file