Auth0 Enterprise Connect#1590
Conversation
avanscoy
added
main-docs
Summary
|
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Workflows to automatically generate PRs for you. |
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Workflows to automatically generate PRs for you. |
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Workflows to automatically generate PRs for you. |
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Workflows to automatically generate PRs for you. |
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Workflows to automatically generate PRs for you. |
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Workflows to automatically generate PRs for you. |
| sequenceDiagram | ||
| actor User | ||
| participant App as Customer App | ||
| participant Auth0 as Auth0 Enterprise Connect |
There was a problem hiding this comment.
There is also a participant: "Customer Auth Server" which is the identity provider for the Customer App.
The Customer Auth Server integrates with Auth0 Enterprise Connect via the b2b_integration.
| participant IdP as Enterprise IdP | ||
|
|
||
| User->>App: Enters email address | ||
| App->>Auth0: Domain discovery (WebFinger) |
There was a problem hiding this comment.
The domain discovery is an Early Access feature - not in Beta.
|
|
||
| 1. Select your agreement as Custom or Personal Account. | ||
| 2. Give the tenant a unique name under Tenant Domain. Your tenant name cannot be changed. | ||
| 3. Under Tenant Type, select **Enterprise Connect Tenant**. |
There was a problem hiding this comment.
The "tenant type" property doesn't exist.
For beta customers, they have to have the feature enabled by Auth0.
There was a problem hiding this comment.
This means the customer needs to contact their Auth0 representative to get their tenant enabled. See: https://oktainc.atlassian.net/wiki/spaces/IAMEF/pages/1015250964/Customer+onboarding+for+Enterprise+Connect+Beta
|
|
||
| 1. Navigate to [**Auth0 Dashboard > Applications > B2B Integrations**](https://manage.auth0.com/#/b2b-integrations). | ||
| 2. Select **Enterprise Connect Integration**. | ||
| 3. In the editor, add an integration name for your existing authorization server. This name cannot be changed. |
| 1. Navigate to [**Auth0 Dashboard > Applications > B2B Integrations**](https://manage.auth0.com/#/b2b-integrations). | ||
| 2. Select **Enterprise Connect Integration**. | ||
| 3. In the editor, add an integration name for your existing authorization server. This name cannot be changed. | ||
| 4. Select the integration type: a customer authorization server you've built, or a managed authorization server from a third-party such as Keycloak. |
There was a problem hiding this comment.
Let's not name a provider (Keycloak) here.
| 4. Select the integration type: a customer authorization server you've built, or a managed authorization server from a third-party such as Keycloak. | ||
| 5. Select a protocol: OpenID Connect (OIDC) or SAML protocols. | ||
| 6. Add the provided endpoint(s) to your IdP's configuration to make Auth0 an OIDC identity provider. | ||
| 7. Add the callback URL from your application so Auth0 can route your users after authentication. |
|
|
||
| ### Update an existing tenant | ||
|
|
||
| Use the following guidelines to enable Enterprise Connect on an existing tenant. |
There was a problem hiding this comment.
As per: https://oktainc.atlassian.net/wiki/spaces/IAMEF/pages/1015250964/Customer+onboarding+for+Enterprise+Connect+Beta
Contact your Auth0 representative to enable an existing tenant.
2 participants
Description
This PR contains the first draft of Auth0 Enterprise Connect, the enterprise-ready B2B layer.
References
Testing
Checklist
CONTRIBUTING.md.