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
I'm hosting ArgoCD at a custom base path (mycompany.org/infra/argocd) and using Keycloak as an external IdP. The configuration functions as expected until I enable PKCE (Proof Key for Code Exchange). Specifically, when enablePKCEAuthentication is set to true in the argocd-cm config map, the ArgoCD frontend incorrectly uses window.location.origin as the redirect URL, as demonstrated in the getPKCERedirectURI function located in utils.ts.
ArgoCD should respect one of the configured parameters (server.rootpath, server.basehref, or url from the argocd-cm or argocd-cmd-params-cm config map) to determine the correct base URL for redirects.
Version
v2.11.0-rc3+20fd621
The text was updated successfully, but these errors were encountered:
Alright thanks. Then the only problem to solve is to discover the root URL in browser and then we can pass to the function mentioned in the issue. I will look into this once I get time.
Checklist:
argocd version
.Describe the bug
I'm hosting ArgoCD at a custom base path (
mycompany.org/infra/argocd
) and using Keycloak as an external IdP. The configuration functions as expected until I enable PKCE (Proof Key for Code Exchange). Specifically, when enablePKCEAuthentication is set to true in theargocd-cm
config map, the ArgoCD frontend incorrectly useswindow.location.origin
as the redirect URL, as demonstrated in thegetPKCERedirectURI
function located in utils.ts.To Reproduce
Login via Keycloak
buttonExpected behavior
ArgoCD should respect one of the configured parameters (
server.rootpath
,server.basehref
, orurl
from theargocd-cm
orargocd-cmd-params-cm
config map) to determine the correct base URL for redirects.Version
The text was updated successfully, but these errors were encountered: