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

Configure a specific realm for application's gatekeeper #699

Open
filippomc opened this issue Aug 10, 2023 · 0 comments
Open

Configure a specific realm for application's gatekeeper #699

filippomc opened this issue Aug 10, 2023 · 0 comments
Assignees

Comments

@filippomc
Copy link
Collaborator

filippomc commented Aug 10, 2023

Currently, the namespace is used as the primary and only option to define the realm.
There are occasions when we want/need to use a different realm coming from external keycloak instance

discovery-url: {{ ternary "https" "http" $tls}}://{{ .root.Values.apps.accounts.harness.subdomain }}.{{ .root.Values.domain }}/auth/realms/{{ .root.Values.namespace }}

So .root.Release.Namespace should be the default if .app.accounts_realm is not defined

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

No branches or pull requests

2 participants