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
I’m configuring Google OIDC for Kratos and running into an issue getting a refresh token. The kratos docs give an example where offline access (to get a refresh_token ) requires the config:
scope:
- offline_access
However, when. using this config Google throws an error saying this scope doesn’t exist. Google docs specify that you just need a param access_type=offline during the auth request. Is there any existing way to configure this param in Kratos? If so, can we add it to the docs? And if not, can we add the ability to add arbitrary params to the auth request?
Reproducing the bug
Steps to reproduce:
Add a Google OIDC provider to Kratos self-hosted.
Add the suggested offline_access (or offline) scope.
Login via Google.
Expected behavior is a that an initial_refresh_token will attach to the identity. Result is that Google throws an error saying whatever included scope isn't allowed/doesn't exist.
Preflight checklist
Describe the bug
I’m configuring Google OIDC for Kratos and running into an issue getting a refresh token. The kratos docs give an example where offline access (to get a refresh_token ) requires the config:
However, when. using this config Google throws an error saying this scope doesn’t exist. Google docs specify that you just need a param
access_type=offline
during the auth request. Is there any existing way to configure this param in Kratos? If so, can we add it to the docs? And if not, can we add the ability to add arbitrary params to the auth request?Reproducing the bug
Steps to reproduce:
offline_access
(oroffline
) scope.initial_refresh_token
will attach to the identity. Result is that Google throws an error saying whatever included scope isn't allowed/doesn't exist.Relevant log output
No response
Relevant configuration
Version
0.11.0
On which operating system are you observing this issue?
macOS
In which environment are you deploying?
Docker Compose
Additional Context
No response
The text was updated successfully, but these errors were encountered: