-
Notifications
You must be signed in to change notification settings - Fork 6.8k
Open
Labels
bugSomething isn't workingSomething isn't workingtriage/pendingThis issue needs further triage to be correctly classifiedThis issue needs further triage to be correctly classified
Description
Checklist:
- I've searched in the docs and FAQ for my answer: https://bit.ly/argocd-faq.
- I've included steps to reproduce the bug.
- I've pasted the output of
argocd version.
Describe the bug
When ArgoCD is configured with a rootPath (also known as [baseHRef]), the OAuth redirect URIs generated for additional URLs do not include the root path. This causes authentication failures when using additional URLs with a configured root path.
Current Behavior
When rootPath is configured (e.g., [argocd]), the redirect URIs for additional URLs are generated as: https://example.com/auth/callback
Instead of the expected: https://example.com/argocd/auth/callback
This only affects additional URLs; the primary URL works correctly.
To Reproduce
- Configure ArgoCD with a rootPath
- Add additional URLs to the configuration
- Attempt to authenticate via one of the additional URLs
- Observe that the OAuth2 redirect URI does not include the root path
- Authentication fails with a redirect URI mismatch error
Expected behavior
All redirect URIs (both for the primary URL and additional URLs) should respect the configured rootPath and generate URLs in the format:
Screenshots
Version
Paste the output from `argocd version` here.Logs
Paste any relevant application logs here.
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
bugSomething isn't workingSomething isn't workingtriage/pendingThis issue needs further triage to be correctly classifiedThis issue needs further triage to be correctly classified