You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -23,7 +23,7 @@ This module requires several new `nginx.conf` directives, which can be specified
23
23
|`auth_jwt_algorithm`| The algorithm to use. One of: HS256, HS384, HS512, RS256, RS384, RS512 |
24
24
|`auth_jwt_location`| Indicates where the JWT is located in the request -- see below. |
25
25
|`auth_jwt_validate_sub`| Set to "on" to validate the `sub` claim (e.g. user id) in the JWT. |
26
-
|`auth_jwt_extract_claims`| Set to a space-delimited list of claims to extract from the JWT and make available as NGINX variables. These will be accessible via e.g: `$jwt_claim_sub`|
26
+
|`auth_jwt_extract_var_claims`| Set to a space-delimited list of claims to extract from the JWT and make available as NGINX variables. These will be accessible via e.g: `$jwt_claim_sub`|
27
27
|`auth_jwt_extract_request_claims`| Set to a space-delimited list of claims to extract from the JWT and set as request headers. These will be accessible via e.g: `$http_jwt_sub`|
28
28
|`auth_jwt_extract_response_claims`| Set to a space-delimited list of claims to extract from the JWT and set as response headers. These will be accessible via e.g: `$sent_http_jwt_sub`|
29
29
|`auth_jwt_use_keyfile`| Set to "on" to read the key from a file rather than from the `auth_jwt_key` directive. |
@@ -93,7 +93,7 @@ auth_jwt_validate_sub on;
93
93
94
94
You may specify claims to be extracted from the JWT and placed on the request and/or response headers. This is especially handly because the claims will then also be available as NGINX variables.
95
95
96
-
If you only wish to access a claim as an NGINX variable, you should use `auth_jwt_extract_claims` so that the claim does not end up being sent to the client as a response header. However, if you do want the claim to be sent to the client in the response, you may use `auth_jwt_extract_response_claims` instead.
96
+
If you only wish to access a claim as an NGINX variable, you should use `auth_jwt_extract_var_claims` so that the claim does not end up being sent to the client as a response header. However, if you do want the claim to be sent to the client in the response, you may use `auth_jwt_extract_response_claims` instead.
97
97
98
98
_Please note that `number`, `boolean`, `array`, and `object` claims are not supported at this time -- only `string` claims are supported._ An error will be thrown if you attempt to extract a non-string claim.
99
99
@@ -103,7 +103,7 @@ For example, you could configure an NGINX location which redirects to the curren
0 commit comments