Skip to content

Commit

Permalink
feat(security): securying endpoints with jwt and oauth2
Browse files Browse the repository at this point in the history
  • Loading branch information
ddeliziact committed Feb 6, 2024
1 parent 64f86bc commit 6c490f6
Showing 1 changed file with 3 additions and 3 deletions.
6 changes: 3 additions & 3 deletions processor/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand All @@ -59,4 +59,4 @@ curl --location 'http://localhost:9000/jwt/token' \
{"token":"<token>"}
```

Use the token to authenticate your requests.
Use the token to authenticate requests protected by JWT: `Authorization: Bearer <token>`.

0 comments on commit 6c490f6

Please sign in to comment.