MitID (DK)

• Enable MitID in your services
• Information about the end user​
• User experience
  
• Private MitID - on behalf of companies
• MitID Erhverv for companies
  

Enable MitID in your services

General information about MitID:

• https://digst.dk/it-loesninger/mitid/

Timeline

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 2021, all users started to receive their MitID identity. During the migration phase from NemID to MitID, it is recommended to support both identification methods. NemID is expected to be phased out by the 1st June 2023.

​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.

Retrieve SSN (CPR)

The CPR number (Danish social security number)​ can be retrieved in this way:

• OIDC: Set the scope parameter to ssn
• SAML: Append the returnssn=true parameter to the identification request.

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 dk_ssn and 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 transaction_id and scope=ssn. For SAML, set returnssn=true and 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 617b5cdc6fb84f16a6022e328d970bb7.

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:

• low
• substantial (default if not set)
• high 

If the 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 substantial.  

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. 

User experience

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 and/or mitid:mitid_erhverv. Read more about the parameters for OIDC and 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/login_hint 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:

Preset ID and Login hint

Reference text

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 either the MitID app or, in case MitID app is not used, in the MitID client.

The reference text may be up to 130 characters. A short description of the parameter can be found here:

• reference_text in OIDC
• reference_text in SAML

Transaction text signing

The transaction text signing feature from the Nets eID broker is offered during a MitID identification. During the identification, the user will be presented with the signing text. The text can either be in HTML or text format. 

Prerequisite for using the feature: 

• Only available using the OIDC protocol towards E-Ident
• The identification request must be signed. Read for more information about signed requests. 

To use the functionality, two parameters must be appended to the identification request: 

• transactiontext - max length 600 char
  
• transactiontext_type - html or text

Allowed HTML tags:

• html, body, head, style, title, div, p, ul, li, h1, h2, h3, h4, h5, h6, table, font, tr, th, td, i, u, b, center, a, q, small

Disallowed:

The ID token will include these new claims:

• transaction_text
• transaction_text_sha256
  
• transaction_text_type

The ID token information is also available at the discovery endpoint. 

HTML signing

Note: The transaction text signing is not the same as the reference text functionality described above or the MitID signing functions through E-Signing.

MitID logo and design

MitID design requirements and logos can be downloaded from the Nets eID broker here. 

​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

1. The customer sends an identification request to E-Ident.
1. If OIDC, the organisation scope must be appended to the request
2. If SAML, the returnorg=true parameter must be appended to the request.
2. The user logs in with his/her MitID. 
3. 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
1. In the background, a lookup to Virk.dk is performed using the CPR number. 
4. ​The user is presented with a list of companies he/she is authorised to represent. 
5. He/she selects the company he/she will represent in this session. 
6. Information about the selected company is returned in the IDToken (OIDC) or Assertion (SAML) as the following values:
1. IDToken  values:
1. authorized_to_represent: CVR number
2. organisation_name: Name of organisation
3. organisation_number: CVR number
2. Assertion attributes:
1. AUTHORIZED_TO_REPRESENT: CVR number
2. ORGANISATION_NAME: Name of organistation
3. ORGANISATION_NUMBER: CVR number​
    

​User interface

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: mitid1,   CPR: 0308451234,   CVRs: 33654545, 44391414
• User name: Trille266,   CPR: 1303103238,   CVRs: 45391514, 33224545, 11658945, 37966533
  

For other users, please contact support.

MitID Erhverv for companies