Token Types

Basic Tokens

The basic token settings determine the length and complexity of short One-Time Passcodes (OTPs) that are generated by the system and sent to users in notification messages, as well as the expiration period for long-form redirect URL tokens. Configure the advanced tokens in the Storefront Gateway Admin Console on the Authentication > Tokens page. You can leave most of these basic settings at their default value, or configure them as needed by your organization. The table below lists and explains all the settings related to the OTP short tokens and the long token URL expiration period.

Setting	Description	Sample Values
Short token case	The character casing for OTPs that are sent to end users for verification. Does not apply if the “Numeric” short token format is selected. Possible values: Upper case, Lower case, Mixed case	The possible values for the short token casing are: - Upper case - Lower case - Mixed case
Short token format	The character format of OTPs that are sent to users to enter on the UI for their verification.	The possible values for the short token format are: - Alphabetic - Numeric - Alphanumeric - Base36
Short token length	The character length of OTPs that are sent to users on the UI for their verification.	The possible values for the short token length are: - 4 characters - 5 characters - 6 characters - 7 characters - 8 characters
Short token expiration period	The time period, defined in minutes, before a short-form token (OTP) expires. The default is 5 minutes.	The expiration period ranges from 0-5 minutes.Note: If the Short token expiration period is set to 0 minutes, the token never expires. This isn’t a recommended practice.
Long token expiration period	The time period before a long-form token (redirect URL) expires, defined in minutes. The default is 28800 (7 days).	The expiration period ranges from 1-28800 minutes.

Advanced Token Settings

After a process completes successfully, Storefront Gateway issues an action Token URL (long-form), and appends this token to the URL set in the advanced settings. The system sends the full URL link (base URL + action Token URL) to the end user in a notification message. When the end user selects the link in the message, the browser redirects the end user to the base URL set in the advanced settings. Configure the advanced tokens in the Storefront Gateway Admin Console on the Authentication > Tokens page by selecting the Advanced token Settings. If you plan to send verification links to end users, your organization must set these advanced token settings. The table below lists and explains all the advanced settings related to long tokens:

Setting	Description	Example
Authenticate user token URL	The token string will be appended to this URL to form the link sent out to end users for verification during authentication. When a user attempts to sign in (using the Authenticate User Process), but they use an authentication identifier (authN ID), Storefront Gateway will issue an action token and append it to this URL to form the full verification link. The system then sends the link to the unverified contact channel in an email or SMS.	https://abc-ulm-qa.m1amdocs.io/user\_confirm?token\_value=
Onboard user with email or mobile token URL	The token string will be appended to this URL to form the link sent out to users for verification during onboarding with email or mobile number. When a user finishes their initial sign-up (using the Onboard User with Email and Mobile Process), Storefront Gateway will issue an action token and append it to this URL to form the full verification link. The system then sends the link to the unverified contact channel in an email or SMS.	https://abc-ulm-qa.m1amdocs.io/complete\_onboard?token\_value=
Onboarding with social media token URL	The token string will be appended to this URL to form the link sent out to users for verification during onboarding with social media. This is something of an edge case. When a user signs up with their social account (using the Onboard and Authenticate with Social Process), the social account provider returns data about that user to Storefront Gateway, and Storefront Gateway passes that information back to your client for the user to confirm. If the user confirms the email or mobile number, then Storefront Gateway trusts the provider and automatically verifies or activates the authentication ID. However, if the user changes the email or mobile value, then they must first verify it before Storefront Gateway fully activates the authentication ID (and the User entity). Therefore, Storefront Gateway will issue an action token and append it to this URL to form the full verification link. The system then sends the link to the unverified contact channel in an email or SMS.	https://abc-ulm-qa.m1amdocs.io/social\_confirm?token\_value=
Add or update authentication identifier token URL	The token string will be appended to this URL to form the link sent out to end users for verification during adding or updating authentication identifiers. When an authenticated end user adds a new email address or mobile number as an authentication ID or update an existing authentication ID (using the Add/Update Email, Mobile, or Alias Process), Storefront Gateway will issue an action token and append it to this URL to form the full verification link. The system then sends the link to the new or updated contact channel in an email or SMS.	https://abc-ulm-qa.m1amdocs.io/new\_authnid?token\_value=
Send verification token URL	The token string will be appended to this URL to form the link sent out to end users for verification when a resend is requested. When a user requests a token resend to replace an expired or misplaced token (using the Send Verification Process), Storefront Gateway will issue a new action token and append it to this URL to form the full verification link. The system then sends the link to the target authentication ID.	https://abc-ulm-qa.m1amdocs.io/user\_resend?token\_value=
Identity recovery token URL	The token string will be appended to this URL to form the link sent out to end users for verification during identity recovery. When an anonymous user requests to reset their password (using the Recover ID Process), Storefront Gateway will issue an action token and append it to this URL to form the full recovery link. The system then sends the link to the target authentication ID.	https://abc-ulm-qa.m1amdocs.io/recover\_id?token\_value=
Onboard and Authenticate token URL	The token string will be appended to this value to form the link sent out to a user to complete the OnboardAndAuthenticate v2 Process.	https://abc-ulm-pdt.m1amdocs.io/reset?token\_value=
Invitation-accept/decline token URL	The token string will be appended to this value to form the link sent out to a User to accept or decline the invite.	https://abc-ulm-pdt.m1amdocs.io/household\_invitation?token\_value=
Admin password recovery token URL	The token string will be appended to this value to form a link sent out to an Admin user to complete the recovery process.	https://abc-ulm-pdt.m1amdocs.io/admin/admin\_reset?token\_value=

Parent topic:Tokens Settings

Home

Introduction

For Merchants

For Resellers

Partner Ecosystem Management

Commerce Engine

Storefront Experience

APIs

Basic Tokens

Advanced Token Settings

​Basic Tokens

​Advanced Token Settings

Basic Tokens

Advanced Token Settings