habsi/authentik
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

website/integrations: replaces all kbd and em tags (#14980)

Browse Source 
Replaces all kbd and em tags
This commit is contained in:
Dewi Roberts
2025-06-09 21:06:37 +01:00
committed by GitHub
parent dea2d67ceb
commit 856ac052e7
89 changed files with 278 additions and 277 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
website/integrations/services/gitlab/index.mdx
View File

@ -52,8 +52,8 @@ To support the integration of GitLab with authentik, you need to create an appli
- **Application**: Provide a descriptive name, an optional group, and UI settings. Take note of the **slug** as it will be required later.
- **Choose a Provider type**: Select **SAML Provider**.
- **Configure the Provider**:
- Set the **ACS URL** to <kbd>https://<em>gitlab.company</em>/users/auth/saml/callback</kbd>.
- Set the **Audience** and **Issuer** to <kbd>https://<em>gitlab.company</em></kbd>.
- Set the **ACS URL** to `https://gitlab.company/users/auth/saml/callback`.
- Set the **Audience** and **Issuer** to `https://gitlab.company`.
- Set the **Service Provider Binding** to `Post`.
- Under **Advanced protocol settings**, select an available signing certificate.
3. Click **Submit** to save the new application and provider.
@ -111,7 +111,7 @@ To support the integration of GitLab with authentik, you need to create an appli
- **Choose a Provider type**: select **OAuth2/OpenID Connect** as the provider type.
- **Configure the Provider**: provide a name (or accept the auto-provided name), the authorization flow to use for this provider, and the following required configurations.
- Note the **Client ID**,**Client Secret**, and **slug** values because they will be required later.
- Set a `Strict` redirect URI to <kbd>https://<em>gitlab.company</em>/users/auth/openid_connect/callback</kbd>.
- Set a `Strict` redirect URI to `https://gitlab.company/users/auth/openid_connect/callback`.
- Select any available signing key.
- Under **Advanced protocol settings**, set the **Subject mode** to `Based on the User's Email`.
- **Configure Bindings** _(optional)_: you can create a [binding](/docs/add-secure-apps/flows-stages/bindings/) (policy, group, or user) to manage the listing and access to applications on a user's **My applications** page.