MitID is a secure and user-friendly digital ID. You use the same login, regardless of whether you want to use your online bank, see your information on borger.dk, download your annual statement from Skat.dk or shop online.

MitID is a flexible and well-thought-out solution. It will be easy to further develop MitID to match a life where technology plays a greater role.

Most of us are already familiar with the NemID app – all we need to do is to download the new MitID app and use it in the same way. But the key card disappears. That is an important difference. It is still important that you never share codes or your user ID for MitID with others. Your MitID is just as important as your passport.

*NemID users will be migrated gradually to MitID during the next 6months*

To Test MitID, please contact our sales: [email protected]

After Registration, Service providers will be provided with Functional and Technical Links to access with Credentials.

Onboarding To MitID

Test Environment:

1.Customer must provide the requested data to test MitID (Please Mention if you are existing Nemid customer)

2.Details will be sent to Nets to approve the service provider to use the test environment services (Nets approval takes up to 4-5 working days)

3.Once approved by Nets, Zignsec will provide you access token with test links details in secured format

4. Test can be accessed for 2 weeks, and Service provider implement the compliances as requested.

*Customers have option to chose between Nemid and MitiD*

 

Production Environment:

1.Customer must provide the requested data to access Live MitID.

2.Details will be sent to Nets to approve the service provider to use the live environment services (Nets approval takes up to 7-8 working days)

3. Broker does Acceptance test to ensure the MitiD compliances are implemented by Service provider during the Nets approval period.

4.Once approved by Nets, Zignsec will provide you access token with details in secured format

POST to Zignsec URL:

https://test-gateway.zignsec.com/

Full URL will be supplied upon completed application supplied by sales

{
  "metadata": {
    "language": "en",
    "popup": false
  },
  "redirect_failure": "https://my_failure_redirect.com",
  "redirect_success": "https://my_success_redirect.com",
  "webhook": "https://my_success_url.com"
}
ParameterDescriptionRequired
providerRequestSee table belowYes
ParameterDescriptionRequired
languageThe requested language. Possible values are DA | EN | KL | da | en | klNo
popupContextIdentifies if the MitId broker page will be opened in a popup or it will be redirect. True – used a popup, false – redirect to another page.No
relaystateThis optional parameter will be returned to you at the redirect back to your server. Use it to link an unique ID of your choice that you can parse. Example: relaystate=zignsec_eid_1234No
targetIf this parameter is supplied the browser session will finally be redirected to this URL-value.No
targetErrortargetError works as target except it is navigated on user cancel or error situations.No
webhookA URL where success/error results will automatically be POST:edNo

Each request returns a response with status and details.

idA unique session identifier generated for each workflow instance.
errorsA JSON array of error conditions, see error handling.
redirectUrlMitId redirect url
{
    "data": {
        "error": null,
        "id": "7f6bb356-7f2b-448a-9d05-9ec782cd765f",
        "redirect_url": "https://zignsec.test.mitid.dk/broker/normal/7f6bb356-7f2b-448a-9d05-9ec782cd765f?popupContext=true",
        "state": null
    }
}

GET to  https://test-gateway.zignsec.com/core/api/sessions/sessionid

How to get notified when workflow is finished:

There is both active and passive notification for when the workflow is finished

  • Callback: Set target and targetError URL parameter in step 1 and you can do the above GET when navigation will occur.
  • Webhook. You can set webhook URL parameter in step step 1 Result will be posted to the URL.
  • Polling: Repeatedly call the above collect-GET until the results contain a final result.
    https://test-gateway.zignsec.com/core/api/sessions

Each request returns a response with status and details.

idA unique session identifier generated for each workflow instance.
statusSession state.
errorsA JSON array of error conditions, see error handling.
resultRepresents result with a signed identity in a JSON Web Token form, see JWT-signature.
{
  "errors": [],
  "event": "session_updated",
  "id": "7f6bb356-7f2b-448a-9d05-9ec782cd765f",
  "integration_id": "MitId",
  "result": {
    "Result": {
      "SignedIdentity": "eyJhbGciOiJSUzI1NiIsImtpZCI6ImUxMjFmNzEyLTlhMTUtNDY2Mi1iZTdlLTkzYzZlYzJhZmJlNiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJodHRwczovL3ppZ25zZWMubWl0aWQuZGsvIiwiaWF0IjoxNjQyNDIwODI0LCJuYmYiOjE2NDI0MjA4MjQsImV4cCI6MTY0MjQyNDQyNCwiaWRlbnRpdHkiOnsiY291bnRyeUNvZGUiOiJESyIsImZpcnN0TmFtZSI6IlR1bGFzaSByYW8gQ2hpbnRhbGEiLCJmdWxsTmFtZSI6IlR1bGFzaSByYW8gQ2hpbnRhbGEiLCJwZXJzb25hbE51bWJlciI6IiIsImRhdGVPZkJpcnRoIjoiMTk3Ni0xMi0zMCIsImFnZSI6NDUsImlkUHJvdmlkZXJOYW1lIjoiTWl0SUQiLCJpZGVudGlmaWNhdGlvbkRhdGUiOiIyMDIyLTAxLTE3VDEyOjAwOjI0LjcyMTkxMTdaIn0sInByb3ZpZGVyRGF0YSI6eyJtaXRpZC5kay5kYXRlX29mX2JpcnRoIjoiMTk3Ni0xMi0zMCIsIm1pdGlkLmRrLmlkZW50aXR5X25hbWUiOiJUdWxhc2kgcmFvIENoaW50YWxhIiwibWl0aWQuZGsuaWFsX2lkZW50aXR5X2Fzc3VyYW5jZV9sZXZlbCI6IlNVQlNUQU5USUFMIiwibWl0aWQuZGsuYWdlIjo0NX19.kRpy1hf0Qx6rdxOjQEHE1E9qVppYKb_XGi8jXH3_6D_GhFoayhrUKZdOaWf7IkaDu93-MAn8PKVih9Ll9vcxGwn2nIuo4xEH7rQwDktAFQD14ZdVs7q_gdzVmhi5AS0NnA93zIPLv3qssyv5KYTvqDdBGz2NiFylkDICcVSa3Qdf08BEEGCfiBu2kVWe9LorMh-h9dkwD6xKXCRa5iuKyM16jgRYZumOFyXnswyZ8v8pKh6sKs_1o_abgMEbJXSx6HTFjhrXlKyf91MuRXrn-iqF-CiWCjpIHhRexyMSTlJPcMnUWTfeJonoB0qFr6xJTAswuj4aXOBvfelkcxb8vQ"
    }
  },
  "status": "Finished"
}

The signed identity can be decoded with JWT Web Token convertors, see JWT convertor tool.

{
  "iss": "https://zignsec.mitid.dk/",
  "iat": 1642420824,
  "nbf": 1642420824,
  "exp": 1642424424,
  "identity": {
    "countryCode": "DK",
    "firstName": "Tulasi rao Chintala",
    "fullName": "Tulasi rao Chintala",
    "personalNumber": "",
    "dateOfBirth": "1976-12-30",
    "age": 45,
    "idProviderName": "MitID",
    "identificationDate": "2022-01-17T12:00:24.7219117Z"
  },
  "providerData": {
    "mitid.dk.date_of_birth": "1976-12-30",
    "mitid.dk.identity_name": "Tulasi rao Chintala",
    "mitid.dk.ial_identity_assurance_level": "SUBSTANTIAL",
    "mitid.dk.age": 45
  }
}