Skip to content

Updated jwt policy docs with new algorithm option #336

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: gh-pages
Choose a base branch
from
Open

Updated jwt policy docs with new algorithm option #336

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 4 additions & 1 deletion docs/policies/jwt.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -6,7 +6,7 @@ doc-order: 5.20

### Description

The JWT policy can verify requests containing HS256 or RS256 signed JSON Web Tokens (as specified in
The JWT policy can verify requests containing HS256, HS384, HS512, RS256, RS384, or RS512 signed JSON Web Tokens (as specified in
[RFC 7519][rfc-jwt])

Each of your Consumers will have JWT credentials (public and secret keys) which must be used to sign their JWTs.
Expand Down Expand Up @@ -160,6 +160,9 @@ The JWT scheme and header are not standardized, therefore they can be overriden
- determines whether the gateway should execute the successive policy in case the auth process fails. If set to false,
the gateway will return an `Unauthorized` response.
- default value: `false`
* `algorithms`:
- If defined, will limit valid JWT's to only those signed with specified algorithms.
- If undefined policy will decode JWT and use algorithm in header to verify.


[rfc-jwt]: https://tools.ietf.org/html/rfc7519
Expand Down