The document provides guidance on setting up Auth0 tenants and accounts for user provisioning and authentication. It recommends:
1) Creating a unique naming convention for each Auth0 tenant associated with a production or development environment.
2) Provisioning separate Auth0 tenants for test, development, and production with custom domains to provide branding and security.
3) Reviewing the use of Auth0 extensions and third-party identity providers to customize user provisioning and authentication capabilities beyond the base Auth0 product.
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as XLSX, PDF, TXT or read online on Scribd
0 ratings0% found this document useful (0 votes)
42 views2 pages
Analyze Checklist
The document provides guidance on setting up Auth0 tenants and accounts for user provisioning and authentication. It recommends:
1) Creating a unique naming convention for each Auth0 tenant associated with a production or development environment.
2) Provisioning separate Auth0 tenants for test, development, and production with custom domains to provide branding and security.
3) Reviewing the use of Auth0 extensions and third-party identity providers to customize user provisioning and authentication capabilities beyond the base Auth0 product.
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as XLSX, PDF, TXT or read online on Scribd
You are on page 1/ 2
# Item Guidance
Architecture Determine tenant naming
AC10 Create a unique Provision name an Auth0 convention production for each tenant Auth0 for each tenant user Accounts and Tenants Tenant Settings Best AC20 domain Provisionyou anneed Auth0todevelopment support tenant for each Practices Set Up Multiple AC30 production tenant you have defined Provision an Auth0 test tenant for each production tenant Environments Set Up Multiple AC40 you Applyhave defined custom domain naming to each Auth0 tenant to Environments AC50 provide branding are associated with and security your Auth0benefits contractual agreement Custom Domains Child Tenant Request AC60 for feature permission parity Review use of Auth0 Extensions to customize and extend Process AC70 Auth0 beyond base product capabilities Extensions User ProvisioningReview use of Auth0 as an identity provider to provide Database Identity AC100 sign-up and user identification user identification by migrating from your existing Providers from a Custom User AC110 legacy identity Review store to provide user identification use of Auth0 Store Authenticate Users AC120 directly from Review use of your existing third-party (legacy) social identity identity storein providers Using Social Your Database Identity AC130 support of user provisioning Review use of Auth0 Hook extensibility to further Providers AC140 customize and extend Auth0's base product capabilities Hooks User Authentication Review Auth0 Universal Login in support of Single AC200 Sign On (SSO) and industry best practice Universal Login Completed (or NA) Notes