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: docs/crd/k8s.nginx.org_policies.md
+3Lines changed: 3 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -58,7 +58,10 @@ The `.spec` object supports the following fields:
58
58
|`jwt.secret`|`string`| The name of the Kubernetes secret that stores the Htpasswd configuration. It must be in the same namespace as the Policy resource. The secret must be of the type nginx.org/htpasswd, and the config must be stored in the secret under the key htpasswd, otherwise the secret will be rejected as invalid. |
59
59
|`jwt.sniEnabled`|`boolean`| Enables SNI (Server Name Indication) for the JWT policy. This is useful when the remote server requires SNI to serve the correct certificate. |
60
60
|`jwt.sniName`|`string`| The SNI name to use when connecting to the remote server. If not set, the hostname from the ``jwksURI`` will be used. |
61
+
|`jwt.sslVerify`|`boolean`| Enables verification of the JWKS server SSL certificate. Default is false. |
62
+
|`jwt.sslVerifyDepth`|`integer`| Sets the verification depth in the JWKS server certificates chain. The default is 1. |
61
63
|`jwt.token`|`string`| The token specifies a variable that contains the JSON Web Token. By default the JWT is passed in the Authorization header as a Bearer Token. JWT may be also passed as a cookie or a part of a query string, for example: $cookie_auth_token. Accepted variables are $http_, $arg_, $cookie_. |
64
+
|`jwt.trustedCertSecret`|`string`| The name of the Kubernetes secret that stores the CA certificate for JWKS server verification. It must be in the same namespace as the Policy resource. The secret must be of the type nginx.org/ca, and the certificate must be stored in the secret under the key ca.crt. |
62
65
|`oidc`|`object`| The OpenID Connect policy configures NGINX to authenticate client requests by validating a JWT token against an OAuth2/OIDC token provider, such as Auth0 or Keycloak. |
63
66
|`oidc.accessTokenEnable`|`boolean`| Option of whether Bearer token is used to authorize NGINX to access protected backend. |
64
67
|`oidc.authEndpoint`|`string`| URL for the authorization endpoint provided by your OpenID Connect provider. |
res.addWarningf("JWT policy %s references a secret %s of a wrong type '%s', must be '%s'", polKey, trustedCertSecretKey, secretType, secrets.SecretTypeCA)
0 commit comments