Skip to main content

Registration

Before you can use the app for authentications and authorisations your end-users need to register the device and activate authentication credentials.

Onboard with ID document and biometric verification

It is also possible to onboard and register the app with ID document and biometric verification using our ReuseID onboarding APIs.

To learn how to do this, see our ReuseID onboarding Quick start guide.

What does it look like for your end-users?​

You can use the image slider below to see what the registration operation looks like for your end-users.

How does the flow work?​

In this flow there are three important concepts to understand:

Activation code​

The app is activated with an activation code. The activation code is generated by MobileID and passed to you in the response when you initiate a registration.

It is your responsibility to display the activation code to the user in the preferred channel; for example, this could be a web page after the user has authenticated themselves.

QR code​

The app has built-in support for scanning a QR code to retrieve the activation code.

  • This provides a better user experience for the end-user, as they can scan the code instead of entering it manually.
  • This makes it easier for you to use longer and more secure activation codes.

To use this, you must generate a QR code and display it to the end-user. The end-user can then scan the QR code with the camera on the device.

Authentication methods​

Once the activation code has been successfully verified the end-user will activate authentication methods. The Authenticator App supports the following authentication methods:

When using the Authenticator App it is required for the end-user to select a PIN. If biometrics are supported in the application configuration, then the end-user will be asked during the registration if they want to activate biometrics.

All methods can be managed (update, enable, disable) by the end-user in the menu in the app.

Operation context​

You can set a post-operation context when using the Start registration endpoint. The post-operation context is passed to the Authenticator App, through a secure channel with end-to-end encryption (E2EE), after a successful registration. Allowing you to pass data in a secure way to your end-user once they have completed the registration.

Want to learn more?

For more information on operation context, see our MobileID feature documentation.

Integration flow​

The sequence diagram below provides an overview of the operations that make up the registration process with the Authenticator App.

Sequence diagram showing MobileID registration with Authenticator App

On this page