User Auth initialization
The User Auth initializer configures authentication and authorization features including login, registration, password management, and session handling. Use initialization to customize authentication flows and user data models.
Configuration options
Section titled āConfiguration optionsāThe following table describes the configuration options available for the User Auth initializer:
| Parameter | Type | Req? | Description |
|---|---|---|---|
langDefinitions | LangDefinitions | No | Language definitions for internationalization (i18n). Override dictionary keys for localization or branding. |
models | Record<string, any> | No | Custom data models for type transformations. Extend or modify default models with custom fields and transformers. |
authHeaderConfig | authHeaderConfig | No | Configures authentication header format for API requests including custom header names and token prefix format (e.g., āBearerā, āTokenā). |
customerPermissionRoles | boolean | No | |
adobeCommerceOptimizer | boolean | No |
Default configuration
Section titled āDefault configurationāThe initializer runs with these defaults when no configuration is provided:
import { initializers } from '@dropins/tools/initializer.js';import { initialize } from '@dropins/storefront-auth';
// All configuration options are optionalawait initializers.mountImmediately(initialize, { langDefinitions: {}, // Uses built-in English strings models: {}, // Uses default data models // Drop-in-specific defaults: // authHeaderConfig: undefined // See configuration options below // customerPermissionRoles: undefined // See configuration options below // adobeCommerceOptimizer: undefined // See configuration options below});Language definitions
Section titled āLanguage definitionsāOverride dictionary keys for localization or branding. The langDefinitions object maps locale keys to custom strings that override default text for the drop-in.
import { initializers } from '@dropins/tools/initializer.js';import { initialize } from '@dropins/storefront-auth';
const customStrings = { 'AddToCart': 'Add to Bag', 'Checkout': 'Complete Purchase', 'Price': 'Cost',};
const langDefinitions = { default: customStrings,};
await initializers.mountImmediately(initialize, { langDefinitions });Customizing data models
Section titled āCustomizing data modelsāExtend or transform data models by providing custom transformer functions. Use the models option to add custom fields or modify existing data structures returned from the backend.
Available models
Section titled āAvailable modelsāThe following models can be customized through the models configuration option:
| Model | Description |
|---|---|
CustomerModel | Transforms customer authentication data including profile information, addresses, and account settings. Use this to add custom fields or modify user data structures. |
The following example shows how to customize the CustomerModel model for the User Auth drop-in:
import { initializers } from '@dropins/tools/initializer.js';import { initialize } from '@dropins/storefront-auth';
const models = { CustomerModel: { transformer: (data) => ({ // Add custom fields from backend data customField: data?.custom_field, promotionBadge: data?.promotion?.label, // Transform existing fields displayPrice: data?.price?.value ? `${data.price.value}` : 'N/A', }), },};
await initializers.mountImmediately(initialize, { models });Drop-in configuration
Section titled āDrop-in configurationāThe User Auth initializer configures authentication and authorization features including login, registration, password management, and session handling. Use initialization to customize authentication flows and user data models.
import { initializers } from '@dropins/tools/initializer.js';import { initialize } from '@dropins/storefront-auth';
await initializers.mountImmediately(initialize, { langDefinitions: {}, authHeaderConfig: {}, customerPermissionRoles: true, adobeCommerceOptimizer: true, models: {},});Configuration types
Section titled āConfiguration typesāThe following TypeScript definitions show the structure of each configuration object:
authHeaderConfig
Section titled āauthHeaderConfigāConfigures authentication header format for API requests including custom header names and token prefix format (e.g., āBearerā, āTokenā).
authHeaderConfig?: { header: string; tokenPrefix: string; }langDefinitions
Section titled ālangDefinitionsāMaps locale identifiers to dictionaries of key-value pairs. The default locale is used as the fallback when no specific locale matches. Each dictionary key corresponds to a text string used in the drop-in UI.
langDefinitions?: { [locale: string]: { [key: string]: string; };};Maps model names to transformer functions. Each transformer receives data from GraphQL and returns a modified or extended version. Use the Model<T> type from @dropins/tools to create type-safe transformers.
models?: { [modelName: string]: Model<any>;};Model definitions
Section titled āModel definitionsāThe following TypeScript definitions show the structure of each customizable model:
CustomerModel
Section titled āCustomerModelāexport interface CustomerModel { firstName: string; lastName: string; email: string; groupUid: string; customAttributes?: Record<string, string>[]; errors?: { message: string }[];}