-
Notifications
You must be signed in to change notification settings - Fork 152
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ERROR: Invalid token response #92
Comments
Me too! |
The response from your identity provider is missing the id_token, which is required by the Open ID Connect specification. Your identity provider does not seem to implement Open ID Connect? https://openid.net/specs/openid-connect-core-1_0.html#TokenResponse |
I had the same problem and it helped to add "openid" as a scope in the plugins settings. |
I have the same issue, and adding 'openid' to the plugin's scope did not fix it. Is there anything else that I should consider? (I've followed this guide to setup keycloak and the openid-connect plugin) |
Did anyone find a solution? |
@joaocg Adding Well, when I say worked, got further -- the defaults for |
With regards to the |
this approach worked for me. After saved the settings when I tried for the first time it failed but it started to work from second request :) |
I'm facing the same issue. |
@lucasmkrolow does Next loud actually support the OpenID Connect standard. Mini Orange also provides solutions for SAML which is not the same thing as OpenID Connect. Can you provide a list of the configuration parameters that are available in NextCloud and what OpenID Connect configuration documentation for NextCloud that you are using? |
Nextcloud uses OAuth 2.0 (that might be the problem). |
Just add |
Sorry for my ignorance!
I'm getting the error message below:
ERROR: Invalid token response
Is there any specific settings I need to make in the plugin?
Or what do I have to do on openid?
The text was updated successfully, but these errors were encountered: