Skip to content

Commit 807f895

Browse files
authored
Update validate-jwt-policy.md
1 parent 4a2fa40 commit 807f895

File tree

1 file changed

+1
-0
lines changed

1 file changed

+1
-0
lines changed

articles/api-management/validate-jwt-policy.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -121,6 +121,7 @@ The `validate-jwt` policy enforces existence and validity of a supported JSON we
121121
* The policy supports tokens encrypted with symmetric keys using the following encryption algorithms: A128CBC-HS256, A192CBC-HS384, A256CBC-HS512.
122122
* To configure the policy with one or more OpenID configuration endpoints for use with a self-hosted gateway, the OpenID configuration endpoints URLs must also be reachable by the cloud gateway.
123123
* You can use access restriction policies in different scopes for different purposes. For example, you can secure the whole API with Azure AD authentication by applying the `validate-jwt` policy on the API level, or you can apply it on the API operation level and use `claims` for more granular control.
124+
* When using a custom header (`header-name`), the header value cannot be prefixed with `Bearer ` and should be removed.
124125

125126

126127
## Examples

0 commit comments

Comments
 (0)