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

Support to specify an external Keycloak instance for SSO #1238

Open
tdkl opened this issue Feb 12, 2024 · 0 comments
Open

Support to specify an external Keycloak instance for SSO #1238

tdkl opened this issue Feb 12, 2024 · 0 comments

Comments

@tdkl
Copy link

tdkl commented Feb 12, 2024

Is your feature request related to a problem? Please describe.
Going through the documentation for the ArgoCD Operator for an OpenShift deployment (https://argocd-operator.readthedocs.io/en/latest/usage/keycloak/openshift/), I wasn't able to find a specific ability to configure an external Keycloak instance to be used for OIDC. The configuration examples consist only of deploying a new and separate Keycloak instance, which isn't even persistent, which I found - interesting. If an organization already has a Keycloak (or other) instance, I don't find it really useful, to create one for every single implementation.

Describe the solution you'd like
Ability to configure an external Keycloak instance to be used for SSO login, like stated on regular ArgoCD documentation: https://argo-cd.readthedocs.io/en/stable/operator-manual/user-management/keycloak/, which isn't an operator deployed instance.

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

1 participant