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
Testing Dex using a config based on examples/config-dev.yaml and the example-app. I built from today's git head with go1.14.3.
I activated the Google section, configured clientID and clientSecret obtained from console.developers.google.com, and I can successfully login using my gmail account. The example app shows:
Is this a known limitation with Google? I wonder if there is some solution for token refresh here, perhaps maintaining the existing "name" claim from the initial authentication if the refresh doesn't supply it? Or just make it completely optional?
name - The user's full name, in a displayable form. Might be provided when:
The request scope included the string "profile"
The ID token is returned from a token refresh
When name claims are present, you can use them to update your app's user records. Note that this claim is never guaranteed to be present. [my emphasis]
The text was updated successfully, but these errors were encountered:
Possibly this is because I'm using type: oidc which comes straight from the config-dev.yaml sample file:
- type: oidc <<<
id: google
name: Google
However, changing to type: google doesn't work without a hosted domain and a delegated API user. Dex tries to open the empty filename:
failed to initialize server: server: Failed to open connector google: failed to open connector:
failed to create connector google: could not create directory service:
error reading credentials from file: open : no such file or directory
Testing Dex using a config based on examples/config-dev.yaml and the example-app. I built from today's git head with go1.14.3.
I activated the Google section, configured clientID and clientSecret obtained from console.developers.google.com, and I can successfully login using my gmail account. The example app shows:
However, if I click the "Redeem refresh token" button, the example app immediately returns:
and the Dex server process logs:
Token refreshing does work with the "mock" connector and the "local" connector, so this seems to be something specific to Google.
I added some debug:
and I can see the response indeed doesn't include a "name" claim.
Is this a known limitation with Google? I wonder if there is some solution for token refresh here, perhaps maintaining the existing "name" claim from the initial authentication if the refresh doesn't supply it? Or just make it completely optional?
I note from Google's documentation:
The text was updated successfully, but these errors were encountered: