Invalid Credentials
If the user provides an invalid password (e.g., the password fails to meet the password complexity rules), then the Process responds with aHTTP 400 status code. The body includes a fieldErrors array with the reason(s) as to what went wrong:
fieldErrors array indicate the following:
- The password fails to include at least one number (0-9)
- The password is on an internal list of commonly banned passwords
- The password fails to meet the minimum length of (8 characters)
- The password fails to include at least one capital (A-Z)
lastStepFailedAction object that repeats the previous Process step’s request. The user can re-attempt their request with a different (ideally stronger) password, and complete their onboarding as normal.
AuthN ID is Already Used
If the user provides an authN ID that already exists in Digital Identity Management, the Process responds with anHTTP 401 status code. The response body includes an operationErrors array with the reason(s) as to what went wrong:
lastStepFailedAction object that repeats the previous Process step’s request. The user can make sure they entered the correct authN ID (email or mobile), retry their request, and complete the Process as usual.
Error Codes
Below is a list of potential error codes that may be returned during the execution of this Process.
Note: See Common Process Error Codes.
Parent topic:Onboard User with Email and Mobile Process

