apps/docs/content/guides/integrate/identity-providers/generic-oidc.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 PrefillAction from './_prefill_action.mdx'; import TestSetup from './_test_setup.mdx';
<Intro components={props.components} provider="your OIDC Provider"/>Click on the ZITADEL Callback URL to copy it to your clipboard. You will have to paste this URL in your external OIDC provider's application settings later.
The exact steps and terminology may vary for each provider. Refer to your provider's documentation if you don't see these options.
https://your-provider.example.com).You can optionally configure the following settings. ZITADEL provides sensible defaults if you leave these unchanged.
Scopes: The scopes define which information ZITADEL will request from the provider. openid, profile, and email are pre-filled.
This information is used to create or update the user within ZITADEL.
ZITADEL ensures that at least the openid scope is always sent.
Use PKCE: If enabled, Proof Key for Code Exchange (PKCE) will be used to secure the authorization code flow in addition to the client secret.
<GeneralConfigDescription components={props.components} provider_account="OIDC provider account" />