Preview of the SSO Provider Create component
Setup Requirements
Auth0 Configuration Required - Ensure your tenant is configured with the
My Organization API. View setup guide
→
Installation
Running the shadcn command also installs the @auth0/universal-components-core
dependency for shared utilities and Auth0 integration.
Quick Start
Full integration example
Full integration example
While this example uses a React SPA, the prop configurations (schema, customMessages, styling, etc.) apply equally to Next.js and shadcn setups.
Props
Core Props
Core props are fundamental to the component’s operation. ForSsoProviderCreate, the only core prop controls what happens after a provider is successfully created.
| Prop | Type | Description |
|---|---|---|
createAction | ComponentAction<...> | Required. Controls post-creation flow. Details |
createAction
Type:ComponentAction<CreateIdentityProviderRequestContentPrivate, IdentityProvider>
The createAction prop is required because it controls where to route the user after a provider is successfully created. Without this, the component wouldn’t know what to do next.
Properties:
disabled- Disable the create button (e.g., while another operation is in progress)onBefore(data)- Called before creation. Returnfalseto cancel. Use for confirmation dialogs or validation.onAfter(data, result)- Called after successful creation. Use for navigation or analytics.
Display Props
Display props control how the component renders without affecting its behavior. Use these to hide sections or enable read-only mode.| Prop | Type | Description |
|---|---|---|
readOnly | boolean | Disable all form inputs. Default: false |
hideHeader | boolean | Hide the header section. Default: false |
Action Props
Action props handle user interactions beyond the core creation flow. These control navigation and wizard step behavior.backButton
Type:{ icon?: LucideIcon; onClick: (e: MouseEvent) => void }
Configures the back button in the component header. Use this to navigate back to your providers list or previous page.
Properties:
icon- Custom Lucide icon component (optional, defaults to ArrowLeft)onClick- Click handler for navigation
onNext / onPrevious
Type:(stepId: string, values: Partial<SsoProviderFormValues>) => boolean
Control wizard step navigation. These callbacks are called when the user clicks Next or Previous. Return false to prevent navigation.
Use cases:
- Validate step data before proceeding
- Log analytics for step completion
- Conditionally skip steps
stepId- Current step identifier ("provider-select","provider-details","provider-configure")values- Current form values
Customization Props
Customization props let you adapt the component to your brand, locale, and validation requirements without modifying source code.schema
Set custom validation rules for provider fields. Rules are organized by provider strategy. All fields supportregex, errorMessage, minLength, maxLength, and required.
Available Schema Fields
Available Schema Fields
Provider Details
name,displayName
okta.domain,okta.client_id,okta.client_secret,okta.icon_url,okta.callback_url
adfs.meta_data_source,adfs.meta_data_location_url,adfs.adfs_server,adfs.fedMetadataXml
google-apps.domain,google-apps.client_id,google-apps.client_secret,google-apps.icon_url,google-apps.callback_url
oidc.type,oidc.client_id,oidc.client_secret,oidc.discovery_url,oidc.isFrontChannel
pingfederate.signatureAlgorithm,pingfederate.digestAlgorithm,pingfederate.signSAMLRequest,pingfederate.metadataUrl,pingfederate.signingCert,pingfederate.idpInitiated,pingfederate.icon_url
samlp.meta_data_source,samlp.single_sign_on_login_url,samlp.signatureAlgorithm,samlp.digestAlgorithm,samlp.protocolBinding,samlp.signSAMLRequest,samlp.bindingMethod,samlp.metadataUrl,samlp.cert,samlp.idpInitiated,samlp.icon_url
waad.domain,waad.client_id,waad.client_secret,waad.icon_url,waad.callback_url
customMessages
Customize all text and translations. All fields are optional and use defaults if not provided.Available Messages
Available Messages
header - Component header
title,back_button_text
title,description
title,descriptionfields.name-label,placeholder,helper_text,errorfields.display_name-label,placeholder,helper_text,error
title,description,guided_setup_button_textfields.okta- Okta fieldsfields.adfs- ADFS fieldsfields.google-apps- Google Workspace fieldsfields.oidc- OIDC fieldsfields.pingfederate- PingFederate fieldsfields.samlp- SAML fieldsfields.waad- Azure AD fields
general_error,provider_create_success
styling
Customize appearance with CSS variables and class overrides. Supports theme-aware styling.Available Styling Options
Available Styling Options
Variables - CSS custom properties
common- Applied to all themeslight- Light theme onlydark- Dark theme only
SsoProviderCreate-headerSsoProviderCreate-wizardProviderSelect-rootProviderDetails-rootProviderConfigure-root
Advanced Customization
TheSsoProviderCreate component is composed of smaller subcomponents and hooks. You can import them individually to build custom SSO provider creation workflows if you use shadcn.
Available Subcomponents
For advanced use cases, you can import individual subcomponents to build custom SSO provider creation workflows. This is useful when you need to embed a single step in a different UI or customize the wizard flow beyond what props allow.| Component | Description |
|---|---|
ProviderSelect | Strategy selection step with provider icons |
ProviderDetails | Name and display name configuration step |
ProviderConfigure | Strategy-specific configuration step |
ProviderConfigureFields | Dynamic form fields based on strategy |
OktaProviderForm | Okta-specific configuration form |
AdfsProviderForm | ADFS-specific configuration form |
GoogleAppsProviderForm | Google Workspace-specific configuration form |
OidcProviderForm | OIDC-specific configuration form |
PingFederateProviderForm | PingFederate-specific configuration form |
SamlpProviderForm | SAML-specific configuration form |
WaadProviderForm | Azure AD-specific configuration form |
Wizard | Multi-step wizard UI |
Available Hooks
These hooks provide the underlying logic without any UI. Use them to build completely custom interfaces while leveraging the Auth0 API integration.| Hook | Description |
|---|---|
useSsoProviderCreate | Provider creation logic and API integration |