Users can authenticate with ZenKey on devices other than their primaries, such as tablets or laptops. These secondary devices rely on the user to complete the authentication process.
Pressing the ZenKey button on a secondary device displays a visual and numeric code as a part of the secondary device authorization process. This code links the secondary device with the primary device.
The following steps correlate to the labels on the diagram above:
- The SDK presents the carrier Discovery UI. If the user authorizes a secondary device from an app on a tablet, the SDK uses a webview.
- Users then scan visual codes or enter the numeric ones into the ZenKey app on their primary device.
- Once approved, the carrier Discovery UI returns a
login_hint_tokento your app’s Redirect URI. This
login_hint_tokenis only returned to a secondary device for use during the authentication request.
- To perform SIM and user authentication, your app requests an authorization code from the appropriate carrier and receives the auth code in its Redirect URI.
- After consenting to share information, your backend server issues a token request to the user for info and other resources.
Updated about 1 year ago