apps/docs/content/guides/integrate/identity-providers/keycloak.mdx
import GeneralConfigDescription from './_general_config_description.mdx'; import Intro from './_intro.mdx'; import CustomLoginPolicy from './_custom_login_policy.mdx'; import IDPsOverview from './_idps_overview.mdx'; import Activate from './_activate.mdx'; import TestSetup from './_test_setup.mdx';
<Intro components={props.components} provider="Keycloak"/>Click on the ZITADEL Callback URL to copy it to your clipboard. You will have to paste it in the Keycloak Client later.
$KEYCLOAK-DOMAIN/auth/admin/$REALM/console/#/$REALM/clients
https://lemur-0.cloud-iam.com/auth/realms/acmeYou can optionally configure the following settings. A useful default will be filled if you don't change anything.
Scopes: The scopes define which scopes will be sent to the provider, openid, profile, and email are prefilled.
This information will be taken to create/update the user within ZITADEL.
ZITADEL ensures that at least the openid-scope is always sent.
Use PKCE: If enabled, the provider will use Proof Key for Code Exchange (PKCE) to secure the authorization code flow in addition to the client secret.
<GeneralConfigDescription components={props.components} provider_account="Keycloak account" />