Enable MitID in your services
MitID will be available in E-Ident as NemID is today, and MitID specific information will be published here as it gets available. The information may be subject to change.
General information about MitID:
MitID was made available through the E-Ident service in October 2021. The E-Ident service are using the broker delivered by Signaturgruppen. From the beginning of October, all users started to receive their MitID identity. During the migration phase from NemID to MitID, it is recommended to support both identification methods.
Information about the end user
The information returned about the end user is listed in the table below. The content may change as the MitID development proceeds.
|Authentication Assurance Level||
|Authorised to represent|
|The organisation number (CVR number) of the organisation the user is authorised to represent. Only available when using the
Private MitID - on behalf of companies function. |
DOB||The user's date of birth.|
|Danish CPR number |
|The end user's social security number (CPR number). For the OIDC protocol, this is returned in both the
ssn claim. |
|Identity Assurance Level||
|Level of assuarance||loa||LOA|
|MitID amr values||mitid_amr||MITID_AMR|
Possible values are:
MITID_UUID||Unique ID for this identity.|
|FULLNAME||Name of user. |
|If the user has a NemID identity, this will be the users unique NemID PID value. |
|Name of the organisation the end user is authorised to represent. Only available when using the
Private MitID- on behalf of companies function. |
Retrieve SSN (CPR)
The CPR number (Danish social security number) can be retrieved in this way:
When this is set, the user will be prompted for their CPR number and this will be returned in the ID Token (OIDC) and Assertion (SAML). The CPR number will be returned in the
ssn claim in the ID Token and as the
DK_SSN attribute in the SAML assertion.
CPR step-up flow
The CPR step-up flow can be used to request the CPR number for already authenticated users. If the CPR number is not already known when the user has authenticated, you can start CPR step-up using the current authentication transaction. The user is then prompted to enter CPR but does not have to re-authenticate. This does not add any additional cost to the transaction.
For OpenID Connect, start CPR step-up by starting an authentication with the parameters
scope=ssn. For SAML, set
transaction_id. This will reuse the previous transaction for the step-up flow.
For OIDC protocol, the
transaction_id parameter value would be
jti claim from ID token.
For SAML protocol, the value for
transaction_id could be found at '/Response/Assertion/@AssertionID' from assertion response. For eg. value of attribute
AssertionID=TI2-617b5cdc6fb84f16a6022e328d970bb7 then transaction_id value would be
It leads to an error response if the CPR step-up flow is requested after the validity of the ID token or SAML assertion. The validity of an ID token and a SAML assertion is 15 minutes.
After the user has inserted the CPR number, you need to request a new ID token or SAML assertion.
Level of assurance and authenticator assurance level
The level of assurance for a specific identification may be set using the
loa_value parameter and the authenticator assurance level may be set using the
aal_value parameter. Both parameters accept these values:
- substantial (default if not set)
loa_value is set, the
aal_value will be ignored. If both the
loa_value and the
aal_value parameter is undefined in the request, the loa_value parameter will as default be set to
The actual used values will be returned as loa and aal claims/attributes in the ID Token/SAML assertion. In addition, ial and mitid_amr claims are returned. See the table above for the possible values.
Note: The customer must validate that the returned values are as expected.
Return the user's NemID PID value
During the migration phase, it may be useful to know the MitID user's NemID PID value if the user has previously had a NemID. It is possible to request that during a MitID identification. To get the user's NemID PID value in return you need to:
- For OIDC, add the scope nemid.pid to the identification request. The PID value will be returned in the nemid.pid claim.
- For SAML, add the request parameter return_nemid_pid=true to the identification request. The PID value will be returned in the NEMID_PID attribute.
If the nemid.pid scope or return_nemid_pid parameter is set, the user will be requested to enter his/her CPR number and the ID Token/SAML assertion will include the user's NemID PID value.
The user may be presented with a choice to log in using MitID, NemID with code card or NemID with code file as in the first picture below. When the user selects MitID he/she will be redirected to the Nets broker for MitID. For E-Ident customers using the Embedded UI option, the service will break out of iframe when the user is directed to MitID.
Note: The E-Ident service was recently updated with a third UI option - pop-up UI. As the user is redirected to the Nets broker for MitID during the identification, pop-up UI may be an option to consider when adding MitID as an identification method. Read more about the pop-up UI.
EID selection page (optional)
The below page is optional. Users may be sent directly to MitID by using the
amr_values/forcepkivendor parameter on the identification request. The parameter value must be set to
mitid. Read more about the parameters for
SAML. The picture below is an illustration of the page for pop-up and standalone UI modes.
MitID client pages
Step 1 - enter user ID. This page may be skipped using the presetid parameter:
Next steps - this may vary dependent on the level of assurance and user preferences. It may be password, OTP, MitID app actions etc. Here illustrated with entering password:
Enter CPR page
Customized UI options
The MitID client UI may be customized by using one of four UI templates. The MitID client is in the square while the customer's logo is in the dotted square.
Templates and customization:
- Basic: Customers may set the background colour.
- Split, Fluid Split and Topbar: Customers may set two different background colours, text color and supply a welcome text and an optionally CPR page text.
- In all templates, the customer logo may be added. The logo file should be 150 x 37 pixels.
Background colours must be given as hex format (example: #ffffff).
Here is an example of a customized page based on the "Split" template:
It is possible to preset the user ID and hence skip the first page in the logon flow. The
presetid=<mitid.uuid> parameter must be appended to the identification request and the parameter value must be set to the user's
mitid.uuid. If that is set, the user will be directed right to the next page. A general description of the presetid parameter is found here.
The user may be shown a reference text throughout the identification. To add a reference text, append the reference_text parameter to the identification request. The reference text will be displayed to user in both the MitID client and in the MitID app.
The reference text may be up to 130 characters. A short description of the parameter can be found here:
MitID logo and design
MitID design requirements and logos can be downloaded from the Nets eID broker
Private MitID - on behalf of companies
A user may choose to use his or hers private MitID when acting on behalf of a company. This feature is also available when using E-Ident. During the logon flow, the user will select the company he or she will represent and this information is sent to the customer.
User flow and implementation
- The customer sends an identification request to E-Ident.
- If OIDC, the
organisation scope must be appended to the request
- If SAML, the
returnorg=true parameter must be appended to the request.
- The user logs in with his/her MitID.
- After the MitID login, the user will be prompted for his/her CPR number. This is used to retrieve information about companies the user are authorised to represent on his/her own
- In the background, a lookup to Virk.dk is performed using the CPR number.
- The user is presented with a list of companies he/she is authorised to represent.
- He/she selects the company he/she will represent in this session.
- Information about the selected company is returned in the IDToken (OIDC) or Assertion (SAML) as the following values:
- IDToken values:
- authorized_to_represent: CVR number
- organisation_name: Name of organisation
- organisation_number: CVR number
- Assertion attributes:
- AUTHORIZED_TO_REPRESENT: CVR number
- ORGANISATION_NAME: Name of organistation
- ORGANISATION_NUMBER: CVR number
After the regular MitID login the user will be presented with a list of companies the user is authorised to represent, and the user selects the one to use in this session:
We have registered these general test users that can be used for testing:
- User name: Mitid2, pwd: asasas12, cpr: 1403532411
For other users, please