You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
'twitter:description': Learn how to use Self-Service Single Sign-On to delegate SSO
11
-
setup to your B2B customers.
10
+
'twitter:description': Learn how to use Self-Service Single Sign-On to delegate SSO setup to your B2B customers.
12
11
'twitter:title': Self-Service Single Sign-On
13
12
---
14
13
Self-Service <Tooltiptip="Single Sign-On (SSO): Service that, after a user logs into one applicaton, automatically logs that user in to other applications."cta="View Glossary"href="/docs/glossary?term=Single+Sign-On">Single Sign-On</Tooltip> (SSO) provides business-to-business (B2B) customers with the tools needed to delegate SSO setup to their enterprise customers. By delegating this task, you can streamline your onboarding process and grant customers more autonomy over their sign-on experience. You can also reduce the time and costs associated with managing SSO across your customer base.
@@ -26,6 +25,8 @@ Users with the following Dashboard roles can engage with this feature:
26
25
27
26
</Callout>
28
27
28
+
To learn more about Auth0’s subscription, read [Manage Subscriptions](/docs/troubleshoot/customer-support/manage-subscriptions). To upgrade your subscriptions, contact your Technical Account Manager or [Auth0 Sales](https://auth0.com/get-started?place=header&type=button&text=talk%20to%20sales).
29
+
29
30
**Supported Providers**
30
31
31
32
Self-Service SSO currently supports the following <Tooltiptip="Identity Provider (IdP): Service that stores and manages digital identities."cta="View Glossary"href="/docs/glossary?term=identity+providers">identity providers</Tooltip>:
@@ -39,6 +40,13 @@ Self-Service SSO currently supports the following <Tooltip tip="Identity Provide
39
40
* Generic OIDC
40
41
* Generic <Tooltiptip="Security Assertion Markup Language (SAML): Standardized protocol allowing two parties to exchange authentication information without a password."cta="View Glossary"href="/docs/glossary?term=SAML">SAML</Tooltip>
41
42
43
+
Self-Service Provisioning currently supports the following identity providers:
44
+
* Okta Workforce Identity (using OIDC)
45
+
* Entra ID
46
+
* Generic OIDC
47
+
* Generic SAML
48
+
49
+
42
50
## How it works
43
51
44
52
Self-Service SSO uses the following components to delegate setup to your customers:
@@ -57,7 +65,7 @@ The steps below provide the general workflow for using Self-Service SSO. These t
57
65
4. Your customer admin launches the self-service assistant via the ticket URL and follows the steps provided to configure their connection and optionally complete domain verification.
58
66
5. A new or updated Enterprise connection pointing to the customer’s application becomes available in your Auth0 tenant.
59
67
60
-
<Frame></Frame>
68
+
<Frame></Frame>
61
69
62
70
## Self-service assistant experience
63
71
@@ -71,43 +79,62 @@ While the exact requirements for configuring SSO vary by IdP, the general workfl
71
79
4.**Claims Mapping**: The customer admin reviews the required and optional user attributes they must capture through their SSO connection. Then, they map these user attributes, or claims, in their IdP system.
72
80
5.**Assign Access**: The customer admin follows the written instructions for their IdP system to grant users or user groups access to your application.
73
81
6.**Test SSO**: The customer admin uses the button provided to test their SSO connection in a new tab. Unless domain verification is enabled, the customer admin can complete the setup process after this step to enable their connection.
74
-
7.**(Optional) Domain Verification**: The customer admin provides their domain and submits it for verification. Domain verification helps enhance overall security by ensuring customers provide legitimate domains during setup. Depending on how you (the Auth0 customer) configured domain verification when generating the access ticket, this experience can vary for customer admins:
82
+
7.**(Optional) Provisioning**: The customer administrator configures user provisioning for their connection by following the provided instructions:
83
+
* Create the application in their IdP.
84
+
* Generate a SCIM bearer token in the assistant and copy the SCIM bearer token and SCIM endpoint URL into their IdP’s configuration.
85
+
* Review the required and optional attributes defined in the User Attribute Profile (UAP). Map these attributes to the corresponding SCIM fields in their IdP system.
86
+
8.**(Optional) Domain Verification**: The customer admin provides their domain and submits it for verification. Domain verification helps enhance overall security by ensuring customers provide legitimate domains during setup. Depending on how you (the Auth0 customer) configured domain verification when generating the access ticket, this experience can vary for customer admins:
75
87
76
-
***If domain verification is set to Required**: The customer admin must complete domain verification before they can enable the connection.
77
-
***If domain verification is set to Optional**: The customer admin can choose to either enter their domain for verification or skip this step. In both cases, the customer admin can enable their connection regardless of its verification status.
78
-
***If domain verification is set to Off:** If domain verification was not enabled at all, this step does not appear to the customer admin and their flow ends with Step 6 above. To learn more, review [Manage Self-Service SSO](/docs/authenticate/enterprise-connections/self-service-SSO/manage-self-service-sso).
88
+
***If domain verification is set to Required**: The customer admin must complete domain verification before they can enable the connection.
89
+
***If domain verification is set to Optional**: The customer admin can choose to either enter their domain for verification or skip this step. In both cases, the customer admin can enable their connection regardless of its verification status.
90
+
***If domain verification is set to Off:** If domain verification was not enabled at all, this step does not appear to the customer admin and their flow ends with Step 6 above. To learn more, review [Manage Self-Service SSO](/docs/authenticate/enterprise-connections/self-service-SSO/manage-self-service-sso).
79
91
80
92
### Example self-service assistant flow
81
93
82
94
The images below demonstrate an example self-service assistant experience. In this example, a customer admin configures SSO with Okta Workforce as their IdP.
<Frame></Frame>
102
+
103
+
**3. Create Application (truncated)**
104
+
105
+
<Frame></Frame>
106
+
107
+
**4. Configure Connection**
108
+
109
+
<Frame></Frame>
110
+
111
+
**5. Claims Mapping**
85
112
86
-
<Frame></Frame>
113
+
<Frame></Frame>
87
114
88
-
**2. Create Application (truncated)**
115
+
**6. Assign Access**
89
116
90
-
<Frame></Frame>
117
+
<Frame></Frame>
91
118
92
-
**3. Configure Connection**
119
+
**7. Test SSO**
93
120
94
-
<Frame></Frame>
121
+
<Frame></Frame>
95
122
96
-
**4. Claims Mapping**
123
+
**8. Provisioning - Create Application**
97
124
98
-
<Frame></Frame>
125
+
<Frame></Frame>
99
126
100
-
**5. Assign Access**
127
+
**9. Provisioning - Configure SCIM**
101
128
102
-
<Frame></Frame>
129
+
<Frame></Frame>
103
130
104
-
**6. Test SSO**
131
+
**10. Provisioning - SCIM Mapping**
105
132
106
-
<Frame></Frame>
133
+
<Frame></Frame>
107
134
108
-
**7. Domain Verification**
135
+
**11. Domain Verification**
109
136
110
-
<Frame></Frame>
137
+
<Frame></Frame>
0 commit comments