Skip to content

Commit 4e6ad4e

Browse files
docs fix
1 parent a1d1fa4 commit 4e6ad4e

1 file changed

Lines changed: 3 additions & 0 deletions

File tree

docs/docs/configuration/idp.mdx

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -663,12 +663,14 @@ To configure **multiple instances of the same provider type** (for example, gitl
663663
"gitlab-cloud": {
664664
"provider": "gitlab",
665665
"purpose": "sso",
666+
"displayName": "GitLab.com",
666667
"clientId": { "env": "GITLAB_CLOUD_CLIENT_ID" },
667668
"clientSecret": { "env": "GITLAB_CLOUD_CLIENT_SECRET" }
668669
},
669670
"gitlab-selfhosted": {
670671
"provider": "gitlab",
671672
"purpose": "sso",
673+
"displayName": "Selfhosted GitLab",
672674
"baseUrl": "https://gitlab.example.com",
673675
"clientId": { "env": "GITLAB_SELFHOSTED_CLIENT_ID" },
674676
"clientSecret": { "env": "GITLAB_SELFHOSTED_CLIENT_SECRET" }
@@ -681,6 +683,7 @@ Each provider keeps the same fields documented above. The only differences are:
681683

682684
- `identityProviders` is an **object** keyed by id instead of an array.
683685
- The id you choose (`gitlab-cloud`, `gitlab-selfhosted`) sets the callback URL, so you register `<sourcebot_url>/api/auth/callback/gitlab-cloud` and `<sourcebot_url>/api/auth/callback/gitlab-selfhosted` with their respective OAuth clients.
686+
- Set an optional `displayName` on each provider to give it a distinct label on the login screen. Without it, both instances fall back to the same provider-type name (for example, "GitLab"), making them hard to tell apart.
684687

685688
<Note>
686689
Each instance needs its own OAuth client (its own `clientId` and `clientSecret`) registered with the matching callback URL.

0 commit comments

Comments
 (0)