Skip to content

Commit a8813e4

Browse files
Merge pull request #6619 from segmentio/sso-replace-old-sso-scim-screenshots
replaced old screenshots and added latest details for Okta setup
2 parents 04a3940 + af41aac commit a8813e4

13 files changed

+17
-14
lines changed
-224 KB
Binary file not shown.
Binary file not shown.
-265 KB
Binary file not shown.
Loading
-37.4 KB
Binary file not shown.
89.8 KB
Loading
77.8 KB
Loading
194 KB
Loading
-810 KB
Binary file not shown.
182 KB
Loading
146 KB
Loading

src/segment-app/iam/scim.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -29,7 +29,7 @@ The other value you need is an API key (sometimes referred to as an Authorizatio
2929

3030
You can find this page in the [settings sidebar of your Segment app](https://app.segment.com/goto-my-workspace/settings/advanced){:target="_blank”}.
3131

32-
![Screenshot of the Segment settings sidebar, with Advanced Settings selected.](images/asset_generate_scim_token.png)
32+
![Screenshot of the Segment settings sidebar, with Advanced Settings selected.](images/generate_sso_token.jpg)
3333

3434
## Features
3535

@@ -107,7 +107,7 @@ For example, you might map `{firstName} {lastName}` from your IdP to `displayNam
107107
> success ""
108108
> **Tip**: You can also link Okta groups to an existing group from in the Segment app using the Okta UI.
109109
110-
![Screenshot of the Segment Settings page, with the Access Management and User Groups tabs selected, and the user group created in the steps above present on the page.](images/scim_edit_groups.png)
110+
![Screenshot of the Segment Settings page, with the Access Management and User Groups tabs selected, and the user group created in the steps above present on the page.](images/scim_edit_group.jpg)
111111

112112
## Microsoft Entra ID Setup Guide
113113

src/segment-app/iam/sso.md

Lines changed: 15 additions & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -25,7 +25,7 @@ To get started, go to your workspace settings and navigate to **Authentication >
2525

2626
![Screenshot of the Connections page, with the Choose a Connection section selected.](images/asset_XCyMZpwo.png)
2727

28-
## Prepare your IdP for the connection.
28+
## Prepare your IdP for the connection
2929

3030
Segment officially supports apps for Okta, Microsoft Entra ID, and OneLogin. Next, find Segment in your IdP's app catalog, and follow the set up instructions they provide.
3131

@@ -53,25 +53,25 @@ Your provider will ask you for a few things from Segment, which Segment provides
5353

5454
After you create the application in your IdP, you can come back to Segment and click "Next".
5555

56-
## Configure Segment to Talk to Your IdP.
56+
## Configure Segment to Talk to Your IdP
5757

5858
Your IdP provides a URL and x.509 certificate. Copy them into their respective fields in Segment.
5959

60-
![Screenshot of the Segment Configure Connection screen.](images/asset_s19XDgWX.png)
60+
![Screenshot of the Segment Configure Connection screen.](images/sso_certificate.jpg)
6161

6262
Then, click "Configure Connection."
6363

6464
You're all set.
6565

66-
## Test your connection with IdP-initiated SSO.
66+
## Test your connection with IdP-initiated SSO
6767

6868
Back at the connections page, make sure your connection is enabled with the switch on the right.
6969

7070
![Screenshot of the Segment Connections page, with one connection currently active.](images/active_connections.png)
7171

7272
You can now test using IdP-initiated SSO (by clicking login to Segment from within your IdP) is working correctly. If not, double check the IdP configuration gotchas section above.
7373

74-
## Require SSO.
74+
## Require SSO
7575

7676
For most customers, Segment recommends requiring SSO for all users. If you do not require SSO, users can still log in with a username and password. If some members cannot log in using SSO, Segment also supports SSO exceptions.
7777

@@ -91,7 +91,7 @@ Segment supports SSO on the login page for emails that match your workspace's do
9191

9292
In order to enable this, you'll need to verify your domain with Segment. To do that, go to the "Domains" tab under "Authentication" in the workspace settings page.
9393

94-
![Screenshot of the Domains page under the Authentication section of the Workspace Settings.](images/asset_MSaDZk2f.png)
94+
![Screenshot of the Domains page under the Authentication section of the Workspace Settings.](images/sso_domain.jpg)
9595

9696
Enter your domain and click "Add Domain." When you click verify, you're given two options to verify your domain, either using a meta tag to add to your `/index.html` at the root, or a DNS text record that you can add through your DNS provider. After you do so and click verify, you can move to the next step.
9797

@@ -142,14 +142,17 @@ Follow these steps in Segment to set up the Okta/Segment SAML integration:
142142

143143
Finish setting up the Okta/Segment SAML integration by carrying out these steps in Okta:
144144

145-
1. In Okta, select the **Sign On** tab for the Segment SAML app, then click **Edit**.
146-
2. Enter the Customer ID you copied in Step 4 of the Segment steps.
147-
3. For **Application username format**, select **Email**.
148-
4. Click **Save**.
145+
1. In Okta, go to Applications > Catalog > Segment & click “Add Integration”.
146+
2. Enter an Application Label for your integration and click Next.
147+
3. Switch to “Sign-On Options” tab and select "SAML 2.0".
148+
4. In “Advanced Sign-on Settings”, enter the Customer ID you copied in Step 4 of the Segment steps.
149+
5. For **Application username format**, select **Email**.
150+
6. Click **Save**.
149151

150-
![Settings in the Okta SSO tab](images/okta_sso.png)
152+
![Settings in the Okta SSO tab](images/okta_sso_step1.jpg)
153+
![Settings in the Okta SSO tab 2](images/okta_sso_step2.jpg)
151154

152-
You've now completed setup. For SP-initiated SSO, follow these steps:
155+
You've now completed setup. For SP-initiated SSO, follow these steps:
153156

154157
1. Go to `https://app.segment.com`.
155158
2. Enter your email, select **Single Sign-On**, then click **Log In**.

0 commit comments

Comments
 (0)