Skip to main content
These Processes enable an anonymous user to recover their User ID and reset a forgotten password. Together, they provide the “forgot password?” user journey. If the user misplaces and forgets their password, they can use their registered email address or mobile number to recover their User ID, and then set a new password to replace lost one. This complete operation is orchestrated by two distinct but related Processes, because the user will need to navigate from the client UI to complete their journey. This second Process ends by signing the user out of all their current open sessions, except for the current one.

Multiple Process Orchestration

Most user journeys are facilitated by a single Process. However, there are some cases where Digital Identity Management orchestrates and links two or more Processes together to complete a given journey. The Recover ID Process starts the user journey and sends a verification action token to the user’s verified email address or mobile number. Once the user redeems that token with the Session Token API, that API invokes the Reset Password Process that allows the user set a new password.

Process Flow

This table describes the Processes at a high level. Preconditions
  • The user has a fully activated User entity with a verified authN ID
  • The user is currently anonymous to Digital Identity Management (i.e., they are not signed in).
Basic Flow
  1. From the sign-in page, the user clicks a Forgot Password? The Recover ID Process starts here.
  2. The user submits an email or mobile registered as their registered authentication identifier (authN ID).
  3. Digital Identity Management quickly looks up the User entity with the authN ID. The following condition apply:
    • If the User entity has more than one registered, verified authN ID, then the Process returns a list of obfuscated authN IDs to select one. The user must select one before the Process proceeds.
    • All emails and mobile numbers returned by the Process are obfuscated according to Obfuscation settings. Thee settings are configured in the MarketONE Admin console.
    • If the User entity only has one authN ID, then the Process simply proceeds.
  4. Digital Identity Management sends a verification action token to the user’s selected email/mobile. The Recover ID Process ends here. The Process return a PKAT to the client.
    • Digital Identity Management sends the user either a long-form, clickable link (with a the token appended to the URL), a short-form One-Time Passcode (OTP), or both.
  5. The user retrieve and redeems the action token. The Reset Password Process starts here.
  6. Digital Identity Management prompts the user to set a new password.
  7. The user submits their new password.
    • Password complexity rules are set in the Admin web application.
Postconditions
  • The user’s password has been reset.
  • If the user had any other open sessions, then they are closed. The end user would then need to re-authenticate.
Possible or Common Errors
  • User not found
    • Note: If the user supplies an invalid authN ID, the Process returns a generic message to the client application, which then shows the user Recovery link has been sent to the provided {email address or mobile number}. This is a security measure to previous malicious actors from determining authN IDs by trial and error.,
  • The provided password does not match password complexity rules.
  • The user has reached the maximum number of failed input attempts.
  • Exceeded the limit OTP entry attempts.

App Settings

Certain aspects of the Process’ behavior are controlled by configurable system settings. Your organization can manage these and other settings in the Digital Identity Management Admin console.

User Journey Diagram

This diagram illustrates the standard “Forgot Password?” user journey using the Recover ID and Reset Password Processes. [product: dim][/product: dim] This diagram also incorporates:

Use Cases

The following use cases provide guided API walkthoughs of these Processes for client developers:

See also

Parent topic:Identity Management Processes