MobileID app

About the MobileID app

The MobileID app offers a simple way to implement and use two-factor authentication on mobile devices, which can be used for authentication (Connect). If combined with SignicatID, electronic signing (Sign) of documents is also supported. The MobileID app is available on Google Play as well as the Apple App Store.

Key features

  • Supports PIN and fingerprint on both Apple and Android devices, as well as Apple Face ID.
  • Can be used as an authenticator as part of SignicatID (SCID).
  • Signing of documents with MobileID is available through Signicat’s signing functionality, if combined with SignicatID.
  • Like the MobileID SDK, the MobileID app relies on Encap, an established and trusted provider of mobile security solutions, for app security. The MobileID app is not the same as the MobileID SDK, however. The MobileID app is a standalone app, whereas the MobileID SDK is integrated with existing business applications.

Integrating with the MobileID app through Signicat

Web integration with the MobileID app is done via the same API as Signicat’s other ID methods. See “Get started with authentication“ for more information. Through the single point of integration, one will get access to Signicat’s wide portfolio of integrated ID methods, not only MobileID, but also other services like identity paper verificationlookups, and video assurance.

Registration

In order to pair the app and an identity, the end-user must go through a registration process.

The identity is established by the merchant through the use of another ID method. The registration process can then be started either in a browser or from another app.

Browser-based registration

Browser-based registration always starts as a regular ID method. The web dialog consists of three steps:

  1. Download the MobileID app – information on how to download the app is provided
  2. Scan QR code – or enter the pairing code manually
  3. Confirmation – confirm or cancel the registration

When the pairing code is scanned or typed into the MobileID app, it will enable Signicat to pair the browser session with the app. When the pairing has been completed, the end-user will be prompted for a PIN code and optionally a fingerprint.

Successful registration results in a deviceId being returned, which will be used for authentication.

Learn more about MobileID app browser-based registration.

Integrated in-app registration

The same steps as above can also be carried out from another mobile app. The merchant’s app should display instructions on how to download the app. But instead of showing the pairing code, it can be sent directly to the MobileID app by opening a link:

https://*.signicat.com/plugins/mobileid-app/?code={pairingCode}

This will trigger the MobileID app on the phone and will automatically perform the pairing.

As is the case for browser-based registration, the end-user will be prompted for a PIN code and optionally a fingerprint.

When the registration has been completed in the MobileID app, a link back to the merchant’s app can be configured for the service. The merchant’s app must ask the end-user for confirmation before it fully trusts the results.

As with browser-based registration, successful in-app registration results in a deviceId being returned, which will then be used for authentication.

Learn more about MobileID app in-app registration.

Authentication

The main purpose of the MobileID app is to be an authenticator.

Browser-based authentication

The deviceId from the registration process must be used to start authentication for a specific user. The deviceId is sent as a “prefilled” parameter to the authentication method.

A push notification is sent to the device, which in turn will start the MobileID app. The end-user will be prompted for the PIN code or fingerprint.

When successfully completed, the same deviceId is returned in the result.

Learn more about MobileID app browser-based authentication.

Integrated in-app authentication

Integration from another app works the same as browser-based authentication. The authentication method must be called with the deviceId in the “prefilled” parameter.

An authentication method used within an app can be configured to link back to the merchant’s app when authentication is finished.

Learn more about MobileID app in-app authentication.

Frequently asked questions (FAQ)

Question Answer
Can the MobileID app be used on a mobile device without a fingerprint reader? Yes, the user will then use a PIN code.
What is the difference between using the MobileID app and enabling native fingerprint support from the OS in your application? Signicat registers the phone as an authentication device and binds the user to the phone and fingerprint (or PIN). The connection between the phone and the server is encrypted and securely handled by Signicat using award-winning technology.
Can the MobileID app be used with Microsoft Surface? No. Only Android and iOS devices are supported.
Does the MobileID app support OIDC and SAML2? Yes
Does the customer need to have SignicatID (SCID)? No, the MobileID app will operate without SignicatID. But SignicatID can be configured to use the MobileID app as an authenticator.
How is this related to the MobileID SDK? The MobileID app is a standalone mobile app that can be used as an authenticator. The MobileID SDK provides an API which allows merchants to implement strong customer authentication in their existing mobile apps.
Who publishes the MobileID app? Signicat AS is the publisher. Going forward, Signicat is considering creating soft-branded apps, where a merchant can be the publisher.