Connecting Keycloak to the applications and platforms teams most often put behind it, using the OIDC and SAML methods each product documents.
Signing in to self-managed GitLab with Keycloak over OpenID Connect: the HTTPS and RS256 signing requirements GitLab documents, mapping Keycloak groups to GitLab access, and which group features need GitLab Premium.
Grafana login through Keycloak with generic OAuth2: role mapping with role_attribute_path, single logout and refresh tokens, and why team sync from Keycloak groups needs Grafana Enterprise or Cloud.
Argo CD sign-in through Keycloak: choosing client secret or PKCE (needed for the argocd CLI), adding a groups claim, and mapping Keycloak groups to Argo CD RBAC roles.
Using Keycloak as the OpenID Connect provider for kubectl and the Kubernetes API server: API server OIDC flags versus the structured AuthenticationConfiguration file, username and groups claims, and pairing it with RBAC.
SAML single sign-on for the Wazuh dashboard with Keycloak as identity provider: the Keycloak client and Roles mapper, the Wazuh indexer saml_auth_domain, and mapping backend roles to administrator or read-only access.
Mattermost SAML sign-in with Keycloak: plans that include SAML, assertion signing and encryption, attribute mappers, and the fact that Mattermost lists Keycloak as a custom rather than officially supported identity provider.
Nextcloud sign-in through Keycloak with the user_oidc app: automatic user and group provisioning from token claims, soft provisioning for existing LDAP users, bearer token validation and backchannel logout.
Protecting APIs at the gateway with Keycloak tokens: the APISIX openid-connect plugin, authorization code, client credentials and token introspection flows, and where Keycloak authorization fits behind the gateway.
Tell us what you're working on, whether it's a deployment, an audit, a security test or a cyber range. You'll speak with an engineer who can help you scope it.