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
As per comments in https://github.com/ory/kratos/blob/master/selfservice/strategy/oidc/provider_config.go
it says we can use for auth_url and token_url, in case when the OAuth2 / OpenID Connect server is not supporting OpenID Connect Discovery. So, i have tried with below config for external oauth provider, and getting error that issuer url cannot be empty.
{
"id": "2c48fa02-142b-4ec2-9be5-56ae4d97b05d",
"error": {
"code": 500,
"status": "Internal Server Error",
"reason": "Unable to initialize OpenID Connect Provider: Get \"/.well-known/openid-configuration\": unsupported protocol scheme \"\"",
"message": "An internal server error occurred, please contact the system administrator"
},
"created_at": "2024-04-25T11:34:37.346379Z",
"updated_at": "2024-04-25T11:34:37.346379Z"
}
It looks like issuer_url is mandatory for generic OIDC. I have tried to perform this with keycloak with individual endpoints, and does work.
rohit-patel-tw
changed the title
Unable to initialize OpenID Connect Provider: oidc: failed to decode provider discovery object
Not able to add OIDC which does not allow OpenID Connect Discovery
May 6, 2024
If your provider is not able to provide the necessary discovery files, please talk to your Ory sales representative or reach out to sales@ory.sh. cc @vinckr
Preflight checklist
Ory Network Project
No response
Describe the bug
As per comments in https://github.com/ory/kratos/blob/master/selfservice/strategy/oidc/provider_config.go
it says we can use for auth_url and token_url, in case when the OAuth2 / OpenID Connect server is not supporting OpenID Connect Discovery. So, i have tried with below config for external oauth provider, and getting error that issuer url cannot be empty.
It looks like issuer_url is mandatory for generic OIDC. I have tried to perform this with keycloak with individual endpoints, and does work.
Reproducing the bug
Relevant configuration
Version
v1.0.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: