Skip to content
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

Cannot configure OIDC SSO to a custom domain #389

Open
garyd2 opened this issue Nov 2, 2022 · 1 comment
Open

Cannot configure OIDC SSO to a custom domain #389

garyd2 opened this issue Nov 2, 2022 · 1 comment

Comments

@garyd2
Copy link

garyd2 commented Nov 2, 2022

Describe the bug
We wanted to use OICD instead of DEX and point it to our SSO provider

To Reproduce
Steps to reproduce the behavior:

  1. Create a customer URL for ArgoCD = eg https://myteamsArgo.company.com
  2. Verify clicking on https://myteamsArgo.company.com works and ArgoCD loads fine with an SSL cert
  3. Configure OIDC in the Operator
  4. Click on the SSO button and you get Invalid redirect URL: the protocol and host (including port) must match and the path must be within allowed URLs if provided

Expected behavior
It redirects me to SSO provider and logs in to ArgoCD Applications, somehow the domain is hardcoded somewhere for a redirect

Screenshots
If applicable, add screenshots to help explain your problem.

Additional context
It works fine on the Domain that the operator deploys eg
https://openshift-gitops-server-openshift-gitops.clustername-1f3d82-0000.us-south.containers.appdomain.cloud/

@anandf
Copy link
Member

anandf commented Jul 24, 2023

Could you provide your ArgoCD CR here ? Have you tried setting .spec.server.host to myteamsargo.company.com and see if that resolves the issue ?
Note: A restart of the ArgoCD server might be required for this change to take effect immediately.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants