Skip to main content

Test eHerkenning

You can test an eID in the Dashboard. Testing allows you to simulate the steps that your end-users follow when authenticating to your digital services.

Note that testing an eID in the Dashboard does not require an authentication protocol. However, you should also test your integration with an authentication protocol, before going live in production.

Prerequisites​

This guide assumes you have completed the steps in these guides:

  1. Initial preparations.
  2. Manage certificates.
  3. Add eHerkenning in the Dashboard.
  4. Set up a service in the service catalogue.
Add a default service

To test a service in the Dashboard, you must first set a default service in the eHerkenning configuration. For instructions on how to do this, see the Set a default service section.

Test eHerkenning in the Dashboard​

To test an eHerkenning authentication flow in the Dashboard, do the following:

  1. In the Signicat Dashboard, navigate to Products > eID and Wallet Hub > eIDs.
  2. Select Test eIDs in the top right corner.
  3. Optional. Choose eHerkenning from the identity provider selection screen. This applies only if you have multiple eIDs enabled in your account.
  4. In the "Choose how to log in" page, choose the eHerkenning supplier that you wish to authenticate with.
  5. Follow the instructions on the login page of the eHerkenning supplier. The steps vary depending on the supplier you choose.

To view an example that uses WeID as a supplier, continue to the next section below.

Example of user journey with WeID​

If you use WeID as a supplier, your authentication flow would look like this:

Select organisation

Note that steps 7 and 8 in the flow above are optional and depend on the organisations a user can log in on behalf of. These are defined in the eHerkenning profile of the user and do not depend on your integration.

Text on the UI​

When a user authenticates with your app using eHerkenning, the UI displays text that contains information such as:

  • Your organisation name
  • Level of Assurance (LoA)
  • Service name

You can view an example of UI text in the web screens displayed above in the Example of user journey with WeID section. In particular, note the following sentences:

  • "You wish to log in to Signicat 1 for Apply for a subsidy 2. To do this you need an authentication method of at least level of assurance EH2 3."
  • "Log in to Signicat 1 for Apply for a subsidy 2"
  • "On behalf of Example Organisation Name B.V. 4 you can use the service Apply for a subsidy 2 at Signicat 1"

In the examples above, the following strings map to values in your service configuration:

  1. Signicat: The name of your organisation. You set this in the eID and Wallet Hub > Settings.
  2. Apply for a subsidy: Service name.
  3. level of assurance EH2: Level of Assurance.
  4. Example Organisation Name B.V.: Optional. The organisation(s) that the user logs in on behalf of. The list here shows the organisations an end-user is a member of. This depends on the eHerkenning profile of the user.

Next steps​

To connect your application to eHerkenning you need to integrate with an authentication protocol.

5. Connect with an authentication protocol
Establish a connection with OIDC, SAML 2.0 or the Authentication API
On this page