@@ -8,8 +8,6 @@ Prominent examples of OpenID Connect providers include Google Accounts, Salesfor
...
@@ -8,8 +8,6 @@ Prominent examples of OpenID Connect providers include Google Accounts, Salesfor
## Caveats
## Caveats
This connector does not support the "groups" claim. Progress for this is tracked in [issue #1065][issue-1065].
When using refresh tokens, changes to the upstream claims aren't propagated to the id_token returned by dex. If a user's email changes, the "email" claim returned by dex won't change unless the user logs in again. Progress for this is tracked in [issue #863][issue-863].
When using refresh tokens, changes to the upstream claims aren't propagated to the id_token returned by dex. If a user's email changes, the "email" claim returned by dex won't change unless the user logs in again. Progress for this is tracked in [issue #863][issue-863].
## Configuration
## Configuration
...
@@ -75,11 +73,10 @@ connectors:
...
@@ -75,11 +73,10 @@ connectors:
# getUserInfo: true
# getUserInfo: true
# The set claim is used as user id.
# The set claim is used as user id.
# Default: sub
# Claims list at https://openid.net/specs/openid-connect-core-1_0.html#Claims
# Claims list at https://openid.net/specs/openid-connect-core-1_0.html#Claims
#
# Default: sub
# userIDKey: nickname
# userIDKey: nickname
# The set claim is used as user name.
# The set claim is used as user name.
# Default: name
# Default: name
# userNameKey: nickname
# userNameKey: nickname
...
@@ -88,9 +85,25 @@ connectors:
...
@@ -88,9 +85,25 @@ connectors:
# However this is not supported by all OIDC providers, some of them support different
# However this is not supported by all OIDC providers, some of them support different
# value for prompt, like "prompt=login" or "prompt=none"
# value for prompt, like "prompt=login" or "prompt=none"
# promptType: consent
# promptType: consent
# Some providers return non-standard claims (eg. mail).
# Use claimMapping to map those claims to standard claims: