From Auth0
Plan an Auth0 enterprise connection import without guessing subjects or copying client secrets.
The merged importer reads supported enterprise connections from the Auth0 Management API through the existing plan, run and cutover engine. No hosted Auth0 tenant interoperability is claimed. The CLI’s Auth0 source integration is separate from these backend operations.
Create the import plan
Section titled “Create the import plan”Send POST /v1/imports with an imports:write secret key, source: auth0 and credentials containing tenant_domain, client_id and client_secret. Use an Auth0 machine-to-machine client with read:connections only. The management reference defines the exact request.
Only canonical <tenant> or <tenant> hosts are accepted. Custom Auth0 domains are refused; do not substitute one even when it serves your application login. Requests use HTTPS, checked public addresses, bounded responses and timeouts, and no redirects. Customer metadata URLs are fetched once without retries; bounded retries apply to the Auth0 Management API.
The client ID and secret are used only during the POST /v1/imports request that reads the tenant, and are never stored, logged or returned. The read finishes within that request, bounded to 50 seconds (Management API retries stop before the deadline), and the import then runs from the frozen plan. Plan limits still apply. Auth0 offset pagination also refuses sources beyond its 1,000-connection capacity rather than silently returning a partial inventory.
Limits on adapter imports
Section titled “Limits on adapter imports”These apply to both Auth0 and CSV SAML imports:
- One at a time. An environment has at most one planned or running Auth0 or CSV SAML import. Another, or a rerun of a failed one, is refused with
import_state_conflictuntil it completes or is cancelled. A refused request reads nothing and consumes no upload. - 20 per hour per environment. More answer HTTP 429
rate_limitedwithRetry-After. - No inline bundles. A
bundlesent with sourceauth0orcsv_samlis refused withparameter_invalid; the adapter builds the bundle itself. - A planned adapter import not run within 24 hours is cancelled automatically.
Review mappings and blockers
Section titled “Review mappings and blockers”| Source strategy | Result |
|---|---|
samlp, adfs, pingfederate |
SAML configuration from supported certificate or safely fetched metadata settings. |
waad, okta, oidc |
OIDC draft marked needs_secret; supply the IdP-issued client secret separately. |
| Unsupported social, database or passwordless strategies | Skipped with a reason in the plan report. |
Connections land inactive and untested. Routing domains are not automatically verified. Review organization mapping and plan.source_skipped, then verify domains, finish configuration, test and activate before switching traffic. Unsupported SAML POST or NameID configuration remains a draft blocker; import never relaxes signature or subject checks.
An optional mapping_upload_id references an unconsumed auth0_mapping UTF-8 CSV upload, at most 5 MiB, with connection_id, organization_external_id and organization_name columns. Explicit mapping takes precedence over source metadata. Without an explicit mapping or source organization, the plan can create one organization per connection; inspect it before running.
Do not infer upstream subjects from user exports
Section titled “Do not infer upstream subjects from user exports”Uploaded Auth0 user exports do not establish unchanged upstream SAML subjects. Export-derived subjects are refused, rather than guessing joins from Auth0 user identifiers. Users re-link at first sign-in; do not promise imported session continuity from a user export. Passwords, Rules, Actions and database connections are not migrated.
Use imported-profile limits and the cutover and rollback checklist before moving an organization. OIDC drafts remain blocked until their missing secret and configuration are supplied and tested.