Closed nTraum closed 1 year ago
Without Discovery
You should provide client_signing_alg
and client_jwk_signing_key
in options, otherwise it will fallback to discovery even you provide false to discovery
option.
With Discovery
Provide jwks_uri
to keys json
or
"#{options[:issuer]}/.well-known/openid-configuration"
should return valid json with configuration, including jwks_uri
Why aren't client_signing_alg
and client_jwk_signing_key
in the docs of the gem?
This should be fixed in 0.5.0 via https://github.com/omniauth/omniauth_openid_connect/pull/133 if discovery
is disabled.
Hi there,
thanks for providing this gem, we at CitizenLab use it for two identity providers that we integrate with.
The authentication process of both providers started to fail with the error described in in #97 some time ago. We tried to fix this by upgrading to omniauth_openid_connect 0.4.0, but after the upgrade we now see the following exception being thrown:
OpenIDConnect::Discovery::DiscoveryFailed
We don't know exactly yet why this is happening, but the interesting part is that this error happens on two completely separate OpenID providers. I don't know the OpenID protocol very well, but we do not have Discovery enabled in any of the two providers, so why is this error being thrown then?
For reference, this is what the configurations of the providers look like:
https://github.com/citizenlabdotco/citizenlab/blob/master/back/engines/commercial/id_bosa_fas/app/lib/id_bosa_fas/bosa_fas_omniauth.rb#L18-L36
https://github.com/citizenlabdotco/citizenlab/blob/master/back/engines/commercial/id_clave_unica/app/lib/id_clave_unica/clave_unica_omniauth.rb#L21-L42
An exemplary stack trace from config 2:
The stack trace seems to indicate that an HTML page is being parsed where JSON is expected. Is this a configuration issue on our side?
Thanks in advance for any hints. We'll investigate further from our side as well and will update the issue in case of any revelations.