Using Keycloak? Use Keycloak OIDC Setup for exact realm, client, group scope, and values settings.
Inputs
Start with the browser-facing deployment URL selected during planning. The OIDC callback URL is always: UsedeploymentUrl from the hub values file. It already includes the scheme, so it can be https://... or http://.... The callback URL registered with the identity provider must match the hub values file exactly.
You also need administrator access to the identity provider, the groups that should map to Metoro roles, and the namespace where the hub will be installed. Use metoro-hub unless your installation intentionally uses a different namespace.
Create The Client
Create a new OIDC application or client for Metoro in your identity provider. Use a confidential web application, authorization code flow, and a client secret. Do not configure implicit flow unless your provider requires it for a separate policy reason. Set the allowed redirect URI to the callback URL above. If your provider asks for allowed web origins, login URL, or post-login redirect origins, use the deployment URL without a path. Request these scopes:Expose Groups
Configure the provider to include group membership in the ID token or userinfo response. The default claim name expected by the chart isgroups.
Use the exact group strings emitted by the provider. If the provider emits full paths such as /metoro-admins, use those full paths in the role mapping. If it emits simple names such as metoro-admins, map those exact names instead.
