It is possible to test features of MitID Erhverv by creating a test organisation in the integration test environment.
Please note that real CPR numbers and names must not be used in the integration test environment; only fictitious CPR numbers and names should be used.
Below, you can read more about:
Have you already created a test organisation and test users? You can log into the MitID Erhverv integration test environment and start testing the available features here:
MitID Erhverv Integration Test Environment: Login
Note that you must log in via the "Test Login" tab.
It is possible to create 2 different types of test organisations:
Before you begin the following 2 conditions must be met:
Before your organisation can create a test organisation with a genuine CVR number, you must log in to MitID Erhverv in the production environment:
Once logged in, the organisation administrator must open the following page in a new tab in the same browser:
MitID Erhverv: Access the integration test environment for your organisation
Alternatively, you can copy the URL into a new tab in the browser where you logged into MitID Erhverv in step 1.
You need to fill in 3 fields:
Then tap the "Approve" button at the bottom of the page.
Now your CVR number has been created in the integration test environment.
The organisation administrator will receive an email containing the following:
Log in to MitID Erhverv integration test environment and begin testing the features here:
Fill in the form on the test portal (no login required):
NemLog-in.dk: Create test user organisation (available only in Danish)
You need to fill out 6 fields:
Once completed the form, tap the "Create" button at the bottom of the page. The "New BO test organisation created with the following data" page will open. Here, you will find details about the test organisation, including a fictitious CVR number and a new test user. You can also find the username and password. These details are required for logging in, be sure to save them both.
The test user can now act as the administrator for the test organisation.
The administrator created in step 1 can now:
Test users can also log in (and sign) with service providers in the MitID Erhverv integration test environment.
In the integration test environment, you can test key features of MitID Erhverv. This environment is, in principle, functionally identical to the MitID Erhverv production environment.
In the integration test environment, you can test features such as:
If you would like to test Local IdP and IdM integration, you should contact the MitID Erhverv Administration for access. When you contact MitID Erhverv Administration, be sure to provide:
The administration can enable the functions for your test organisation with the information provided.
To have test users in your test organisation in the MitID Erhverv integration test environment, you must first create fictitious private test users in the MitID Simulator.
In the MitID Simulator, you must enter following details:
Note that you can instead tap "Autofill," which will automatically fill in the following details:
Tick the box "Private MitID" if the user is to be used for private MitID login. This should be done in most cases, as it is the recommended way to manage test business users. By ticking the box "Private MitID", the test user is created as a private identity in the MitID Simulator. The user can then be linked as a business user in the test environment and use the private MitID created in the MitID Simulator as a login method.
Test certificates are easiest to order via the MitID Erhverv application interface in the integration test environment or through the associated APIs. Additionally, you can download an example of a system certificate, although it will not be linked to your own test organisation's CVR number.
OCES3 System Certificate (.p12)
Password: c5,PnmF8;m4I
The key files generated via MitID Erhverv are in PKCS#12 format and encrypted using the AES algorithm. This may cause issues with older software. If this happens, the files can be repacked into a different encryption algorithm using tools like:
The root certificate and the certificate issued for the test can be retrieved from the test certificate's .12 file using the relevant software for the purpose.
Blacklists and OCSP services in the OCES3 infrastructure are not accessible via fixed IP addresses due to DDoS protection. As a result, any firewall rules for outgoing traffic in your organisation must be defined based on the host name and not on IP addresses.
Organisations wishing to manage their users within their own local systems can integrate with the IdM API in MitID Erhverv. This enables you to create users in your local systems, and they will also be automatically created in MitID Erhverv. Please note that a local user can only access self-services via Local IdP once the user has been created in MitID Erhverv following the synchronisation between the local system and MitID Erhverv.
If you would like to test IdM integration, contact the MitID Erhverv Administration for access via email providing the following details:
MitID Erhverv Administration can then enable the necessary features for your test organisation.
MitID Erhverv Administration: Email
The documentation package for integration with the IdM API in MitID Erhverv has been updated to include the requirement for email validation. If you issue certificates containing an email address, you must validate the email provided.
The package comprises:
Additionally, the package contains separate documentation for the Certificate API, which allows you to issue and renew certificates.
Download the documentation package:
Documentation package (V1.12) for IdM and certificate API (zip) (updated 21 November 2024)
Please note that users do not have certificates attached by default in NemLog-in, as certificates are not used for login.
When synchronising large numbers of users (thousands) via the API, it is recommended to do so overnight or, at the very least, spread the synchronisation over an extended period (e.g. 60-120 minutes). Furthermore, avoid authenticating every individual user during updates. Instead, update multiple users using login session.
There is a limit on API usage based on the number of calls within a specific time frame. This measure is implemented to prevent exessive system load and maintain operational stability. If this limit is exceeded, the system will return an HTTP 429 (Too Many Requests) response code.
For example, attempting to synchronise a large number of users (thousands) in a short period may trigger this error. Should this occur, we recommend halting the synchronisation immediately and resuming it later, ensuring a delay between requests to avoid further issues.
If you would like to test Local IdP, please contact MitID Erhverv Administration to request access. When doing so, please ensure you provide the following details:
MitID Erhverv Administration can then enable the necessary features for your test organisation.
MitID Erhverv Administration: E-mail
When integrating a Local IdP and assuming responsibility for authenticating your local users, the OIOSAML Local IdP Profile must be adhered to for integration with NemLog-in's broker.
Below, you will find guides, specifications, and metadata for the integration test environment for NemLog-in as a SAML Service Provider, which should be imported into your Local IdP:
Integration with NemLog-in – Local IdP (pdf) (latest updated 14 December 2023)
Remember to:
The metadata required for the integration test environment can be found on NemLog-in.dk:
An organisation administrator within your organisation can manage your test organisation in the integration test environment. In MitID Erhverv integration test environment, you can view the administrators you have created.
You can add a new organisation administrator if:
The organisation administrator must open the following page in a new tab in the same browser:
MitID Erhverv: Access the integration test environment for your organisation
Under "Integration test environment details", you are required to fill in the:
Tap "Approve".
The new administrator will now be created with a username and password. Please make a note of them and send the details to the new administrator.
Please note:
Your organisation can update the API key in situations such as if you:
The organisation administrator must open the following page in a new tab in the same browser:
MitID Erhverv: Access the integration test environment for your organisation
Under "Integration test environment details", you mustto provide a new API key, ensuring that only your organisation can call the API.
Then, tap "Approve".
The API key for your organisation in the integration test environment will now be updated.
Please note the organisation administrator does not need to enter the current API key in order to change it.
NemLog-in has a pre-production environment where you can set up test organisations in MitID Erhverv. This environment is designed for early testing of upcoming features for early testing of upcoming features that are progressing through NemLog-in’s environments but have not yet been released in the integration test environment.
Testing in the pre-production environment follows the same process as outlined above, but you must set up a test organisation in the pre-production environment.
Please note that there are no service level objectives in the pre-production environment, so it may be unstable.
To learn more about setting up a test organisation in the pre-production environment, visit:
NemLog-in.dk: Pre-production environment for user organisations (Devtest4)
If your organisation is a service provider that:
you can refer to the guides on NemLog-in's service provider homepage, which also includes instructions for testing the integration with a self-developed service (login and signing):
NemLog-in.dk: Integration test environment (Available only in Danish)
The following topics may also be relevant to your organisation if it uses advanced functionality in MitID Erhverv.