Closed abdennour closed 3 years ago
Hey, you need to also set url
in configuration, refer to https://argoproj.github.io/argo-cd/operator-manual/user-management/#2-configure-argo-cd-for-sso
I believe there is an appropriate parameter for the Helm chart as well.
@jannfis I did .. But which URL ? crowd or argocd
Oh, sorry, forget what I said - it clearly is about the connector. Sorry.
So, turns out we are using Dex v2.22.0 and Atlassian Crowd connector was introduced in v2.23.0. So you can either try your luck with a manual upgrade of Dex image to v2.23.0 (might not work, for whatever reasons tho) or wait for us to provide an update.
Let us know if it works, and we can upgrade dex.
Yep @jannfis ! I've checked dex release notes, and i can see that Crowd is well supported since v2.24.0. I updated dex tag to latest in helm values
dex:
image:
tag: v2.25.0
And now it works like a charm 🎊 🎊🎊
@jessesuen you can upgrade Dex to support Atlassian Crowd. However, you will need to test other connectors with this upgrade.
@jessesuen I need your urgent support for https://github.com/argoproj/argo-cd/discussions/7989
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 Argocd cannot handle authentication thru Dex + Atlassian crowd connector
Clicking on login button, it takes time then, it show :
To Reproduce
Using argocd helm chart :
server.config.dex\.config
to be:helm install ...
Expected behavior
Screenshots
N/A
Version
Logs
kubectl -n argocd logs -f argocd-dex-server-584d58b547-dvgx6
Dex throw out in the logs