Repository navigation
Replies: 2 comments 1 reply
|
I have no idea what you are doing because there is no context for the issue or the version of Keycloak (KC) you are using. However, the error shown is related to a failed HTTP request to the OIDC discovery endpoint. The |
|
I encountered a similar problem. Here's the ArgoCD configuration: config:
oidc.config: |
name: Keycloak
issuer: http://keycloak.keycloak.svc.cluster.local/realms/ml-team
clientID: argocd
clientSecret: $oidc.keycloak.clientSecret
requestedScopes: ["openid", "profile", "email", "groups"]when called, this link returns:
And an error when trying to log in: Address keycloak.keycloak.svc.cluster.local is the internal Kubernetes address behind the Traefik proxy. Consequently, argocd can't access https://keycloak.k3s-lab.com In theory, the argocd settings should look something like this: |
|
There are quite a few discussions on the issuer check: see this issue / comment and the linked discussions #41858 (reply in thread) |
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Description
I recently deployed Argocd for my org and as a way of authenticating, we decided to adopt Keycloak for verification as it is used extensively within the org. Looked at the argocd documentation in order to set it up but each time I click on the Keycloak on the Argocd UI, I immediately get this error
'''Failed to query provider "https://keycloak_url/auth/realm name": 404 Not Found: {"error":"RESTEASY003210: Could not find resource for full path: https://keycloak_url/auth/realm name/.well-known/openid-configuration"}'''
and in other cases
Failed to query provider "https://keycloak_url/realm_name": 404 Not Found:
Resource not found
I have thoroughly checked through including creating the client, client role and group again but the issue still persists. Any ideas ?
All reactions