-
Notifications
You must be signed in to change notification settings - Fork 5.4k
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
OICD login stopped working (at least for Auth0) #8221
Comments
Thanks, was searching like crazy to see if I did the setup wrong but reverting to 2.2.2 fixed it for me. |
@TheGeka, do you also use Auth0 or another OIDC provider? |
I use Keycloak as OIDC provider. |
I spoke too soon Working cluster
Not Working cluster:
|
Accidentally closed via description text containing "fixed" |
The https://raw.githubusercontent.com/argoproj/argo-cd/8b57bc990cd72c6475e2ae88126a1ed57e2460a3/manifests/ha/install.yaml uses the latest image tag. So it pulls the most recent version of the Argo CD. We've recently migrated to |
If you are trying to resolve an environment-specific issue or have a one-off question about the edge case that does not require a feature then please consider asking a question in argocd slack channel.
Checklist:
argocd version
.Describe the bug
I have ArgoCD configured for OICD login via Auth0. This has been working fine, but today it stopped working. After a lot of troubleshooting, I noticed the image version had updated. I have a cluster that is working and using an older image:
a17d6af8dc8461e1dc637d99c651b07e083e7df5f92bc2994d0b0cf74929b961
never redirects to Auth0.3115fcc3a25357c05185802568f15fdc556dc3eab38a1fea11aae8cbd5e763ba
works, although the image is not listed.To Reproduce
A list of the steps required to reproduce the issue. Best of all, give us the URL to a repository that exhibits this issue.
kustomization.yml
oidc.config
Then open the UI, and open the browser's Network Inspector, click LOG IN VIA AUTH0. You'll notice you are never redirected away from the ArgoCD URL, and end up straight back at the login page.
Expected behavior
Clicking the LOG IN VIA AUTH0 button should redirect to Auth0, and on successful consent/token issue, redirect back to
/auth/callback
.Screenshots
Version
Logs
I have pinned to a specific version, but the K8s manifests use
latest
. I think these should be pinned (at least to a minor version).My workaround is to add the following to my
kustomization.yml
The text was updated successfully, but these errors were encountered: