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

Add default client scopes to auto generated keycloak clients #306

Closed
ericwyles opened this issue Mar 27, 2024 · 1 comment
Closed

Add default client scopes to auto generated keycloak clients #306

ericwyles opened this issue Mar 27, 2024 · 1 comment
Labels
enhancement New feature or request

Comments

@ericwyles
Copy link
Contributor

Is your feature request related to a problem? Please describe.

When using SSO Secret Templating (#263) to create clients, we need a way to set default scopes on the client. This is because Keycloak is now requiring the openid client scope to be present on all tokens in order for the userinfo call to succeeed (See: defenseunicorns/uds-identity-config#38)

Describe the solution you'd like

Additional context

The openid client scope also has to be configured on the keycloak realm before it can be added to specific clients. Issue open here for that: defenseunicorns/uds-identity-config#38

Keycloak change that requires this explained here: https://www.keycloak.org/docs/latest/upgrading/index.html#userinfo-endpoint-changes

@ericwyles
Copy link
Contributor Author

ericwyles commented Mar 28, 2024

This is not necessary as long as the client scope already exists on the realm. See defenseunicorns/uds-identity-config#38

Example config:

spec:
  sso:
    - name: Mattermost Client
      clientId: mattermost-client
      redirectUris:
        - "https://chat.uds.dev/*"
      defaultClientScopes:
        - "openid"

Closing this issue since it is already covered using defaultClientScopes as shown above.

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

No branches or pull requests

1 participant