This section has some important tips and points to consider when implementing Mobile Connect in your application or service.
Make sure you cover all possible scenarios in your implementation. Below is a a summary of the common scenarios:
First Time Users
Mobile Connect Setup during Account Creation: The user should be able to set up Mobile Connect as a sign-in option for his/her account in your application/service.
Setting up Mobile Connect after previously creating an account: The user should be able to add Mobile Connect as a sign-in option for his/her account in your application/service anytime after creating the account
Removing Mobile Connect: The user should be able to remove Mobile Connect as a sign-in option for your application/service
Working with Existing Users
Pairing Accounts for existing users: When a user adds Mobile Connect as a sign-in option for your app/service, you should pair the existing user account with the Mobile Connect account of the user using the PCR as the key identifier.
In-life Account Management: These are some common in-life scenarios and the expected outcomes for the Mobile Connect account
Scenario Expected Outcome Notes Account is locked Log in using Mobile Connect fails No difference from log in with username and password Password has expired Log in using Mobile Connect succeeds Users will be able to continue using Mobile Connect indefinitely as long as their account is Active User resets the password Mobile Connect deactivated User can re-enable Mobile Connect after resetting password Account is Dormant Log in using Mobile Connect fails User must reactivate account via email, reset the password and then enable Mobile Connect using the new password. Account is Disabled Mobile Connect deactivated Deactivate will happen as part of the disable process. Account is New or Inactive Log in using Mobile Connect fails Mobile Connect will not be active (because Inactive means previously disabled, New means never logged in). User must first activate before enabling Mobile Connect.