Skip to content

Commit d2e61aa

Browse files
authored
Enhance SCIM setup instructions for Okta (#1744)
1 parent 139064a commit d2e61aa

1 file changed

Lines changed: 18 additions & 0 deletions

File tree

docs/admin/scim.mdx

Lines changed: 18 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -72,6 +72,24 @@ To configure:
7272

7373
To set up user provisioning in [Okta](https://help.okta.com/en-us/Content/Topics/Apps/Apps_App_Integration_Wizard_SCIM.htm), you must first set up a new app integration of the "SAML 2.0" type, then configure it to use SCIM. Here are the steps to do this:
7474

75+
<Callout type="note">
76+
Please note: Okta offers two different provisioning configuration UIs depending on the
77+
integration type: **SCIM Connection** (used with standard integrations) and
78+
**Connector Configuration** (used with custom connectors via the Okta
79+
provisioning agent). The steps below apply to both, but the way the
80+
`Authorization` header is entered differs slightly:
81+
82+
- In the **SCIM Connection** UI, there is a dedicated `Bearer` prefix field
83+
alongside the token input — enter only the raw token in the token field.
84+
- In the **Connector Configuration** UI, there is a single text field for the
85+
full header value — you must enter the full string `Bearer {your token}`
86+
(including the `Bearer ` prefix) in that field.
87+
88+
In both cases, the Sourcegraph SCIM server requires the `Authorization` header
89+
to be in the format `Bearer {your token}`. Omitting the `Bearer ` prefix will
90+
result in a `401 Unauthorized` error.
91+
</Callout>
92+
7593
1. Follow our [SAML guide](/admin/auth/saml/okta) to set up a new app integration with SAML, then open the integration you just created.
7694
- If you already have the integration, just open your existing app integration.
7795
1. Go to the "General" tab and click "Edit" in the "App Settings" section.

0 commit comments

Comments
 (0)