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
|`oidc.issuer-uri`|| Issuer URI, should be the same as the `iss` field of the tokens |
71
-
|`oidc.skip-tls-verify`|`false`| Disable tls cert verification when retrieving keys from the IDP. Not intended for production. Consider mounting the proper `cacerts` instead of disabling the verification. |
72
-
|`oidc.jwk-uri`|| JWK URI, useful when auto discovery is not available or when `iss` is not consistent across tokens (e.g [Google](https://stackoverflow.com/questions/38618826/can-i-get-a-consistent-iss-value-for-a-google-openidconnect-id-token)) |
73
-
|`oidc.public-key`|| Public key used for validating incoming tokens. Don't provide this if you set `issuer-uri` or `jwk-uri` as it will be bootstrapped from that. This is useful if Onyxia-API has trouble connecting to your IDP (e.g self signed certificate). You can usually get this key directly by loading the issuer URI : (e.g `https://auth.example.com/realms/my-realm`) |
65
+
|`oidc.issuer-uri`|| Issuer URI. Onyxia-API will use this URL to retrieve the public key for token validation. e.g for Keycloak : `https://keycloak.example.com/auth/realms/REALMNAME`|
74
66
|`oidc.clientID`|| Client id to be used by Onyxia web application |
75
-
|`oidc.audience`|| Optional : audience to validate. Must be the same as the token's `aud` field |
76
67
|`oidc.username-claim`|`preferred_username`| Claim to be used as user id. Must conform to [RFC 1123](https://kubernetes.io/docs/concepts/overview/working-with-objects/names/#dns-label-names)|
77
68
|`oidc.groups-claim`|`groups`| Claim to be used as list of user groups. |
78
69
|`oidc.roles-claim`|`roles`| Claim to be used as list of user roles. |
70
+
|`oidc.audience`|| Optional : audience to validate. Must be the same as the token's `aud` field |
71
+
|`oidc.skip-tls-verify`|`false`| Disable tls cert verification when retrieving keys from the IDP. Not intended for production. Consider mounting the proper `cacerts` instead of disabling the verification. |
72
+
|`oidc.public-key`|| Optional: If for some reason you don't want Onyxia-API to bootstrap configuration by requesting the `issuer-uri` then you can manually provide the public key used for validating incoming tokens. |
79
73
|`oidc.extra-query-params`|| Optional : query params to be added by client. e.g : `prompt=consent&kc_idp_hint=google`|
74
+
|`oidc.scope`|`openid profile`| Optional : Specifies the OIDC scopes to be requested by the Onyxia client. `"openid"` is always requested, regardless of this setting. |
75
+
|`oidc.workaroundForGoogleClientSecret`|| For some reasons, Google OAuth requires providing a client secret even for public clients. ⚠️ Use this configuration only if using Google OAuth ! ⚠️ For all other providers you should not have client secret as the Onyxia client is public. Example client secret format: " `GOCSPX-_xxxxxxxxxxxxxxxxxxxxxxxxxxx`|
0 commit comments