For the complete documentation index, see llms.txt. You can also append .md to any page URL to get its markdown version.
Skip to main content
For the complete documentation index, see llms.txt.

For the complete documentation index, see llms.txt

DigiD app-to-app flow

In an app-to-app flow, the end-user authenticates in the DigiD app and then returns to your native mobile app. Authentication takes place on the same device, and the end-user does not type credentials into a browser.

Use the Signicat OIDC SDK to manage the underlying OIDC authentication.

What does it look like?

For an illustration of what the end-user sees, see Example app-to-app.

Prerequisites​

Before you start, you must first complete your DigiD integration. The app-to-app flow is an addition to a working DigiD connection, not a replacement for one.

Follow the DigiD integration guide to:

  • Sign the necessary agreements.
  • Order your certificates.
  • Set up DigiD in pre-production.

How it works​

The SDK manages OIDC authentication. Your app handles the authentication result returned by the DigiD app:

  1. Your app sets acrValues to idp:digid-app in its OIDCConfiguration. This tells Signicat to route the authentication to the DigiD app rather than to a browser-based login.
  2. Your app calls login() on Android or login(appLinkHandler:) on iOS, which starts the OIDC flow.
  3. DigiD authenticates the end-user in the DigiD app.
  4. The DigiD app returns to your app through a universal link on iOS or an App Link on Android, with the authentication result.
  5. Your app validates that link and resumes the OIDC flow by forwarding the result to the Signicat broker.
  6. The SDK completes the token exchange and returns a session.

You must implement steps 4 and 5. For an example, see the OIDC SDK demo app section below.

OIDC SDK demo app​

Use the platform-specific demo implementations as a reference for your app:

On this page