apps/docs/content/guides/integrate/identity-providers/gitlab.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'; import UnlinkedOAuth from './_unlinked_oauth.mdx'; import PrefillAction from './_prefill_action.mdx';
<Intro components={props.components} provider="GitLab"/>Click on the ZITADEL Callback URL to copy it to your clipboard. You will have to paste it to the GitLab Application later.
After clicking "Save application", you will see the detail page of the application you have just created. To be able to connect GitLab to ZITADEL you will need a client ID and a client secret. Save the ID and the Secret, you will not be able to copy the secret again, if you lose it you have to generate a new one.
Go back to the GitLab provider template you opened before in ZITADEL. Add the client ID and secret you created before when you registered your GitLab application.
You 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.
https://github.com/zitadel/actions/blob/main/examples/gitlab_identity_provider.js