Up-party - Connect NemLog-in with SAML 2.0

FoxIDs can be connected to NemLog-in (Danish IdP) with a up-party SAML 2.0. Where NemLog-in is a SAML 2.0 Identity Provider and FoxIDs is acting as an SAML 2.0 Relying Party (RP) / Service Provider (SP).

NemLog-in give your users access to authenticate with MitID.

NemLog-in (currently called NemLog-in3) is a Danish Identity Provider (IdP) which uses the SAML 2.0 based OIOSAML 3. FoxIDs support NemLog-in / OIOSAML 3 including logging, issuer naming, required certificates and it is possible to support NSIS.

NemLog-in test and production environment:

A sample showing the NemLog-in integrations is configured in the FoxIDs test-corp with the up-party name nemlogin_oidc. The configuration uses a separate track where the NemLog-in integrations is configured and converted from SAMl 2.0 to OpenId Connect.
You can test NemLog-in login with the AspNetCoreOidcAuthorizationCodeSample sample application by clicking OIDC NemLog-in Log in or by clicking Log in and then Danish NemLog-in.

Consider separate track

NemLog-in requires the Relying Party (RP) to use a OSES certificate and a high level of logging. Therefore, consider connecting NemLog-in in a separate track where the OCES certificate and log level can be configured without affecting any other configuration.

Two FoxIDs tracks can be connected with OpenID Connect. Please see the connect FoxIDs with OpenID Connect guide. The track with a up-party connected to NemLog-in is called the parallel FoxIDs track in the guide.

Certificate

NemLog-in requires all requests (authn and logout) from the Relying Party (RP) to be signed. Furthermore, NemLog-in requires the RP to sign with a OCES certificate. It is not possible to use a certificate issued by another certificate authority, a self-signed certificate or a certificate issued by FoxIDs.

A OCES certificate is valid for three years thereafter it manually has to be updated.

Add the .P12 OCES certificate in FoxIDs Control Client:

  1. Select (or create) the track to be used for NemLog-in
  2. Select the Certificates tab
  3. Click the arrow down on the Swap certificate button and then in the Contained certificates section click Change container type

Add OCES certificate

  1. Then click on the primary certificate, then write the password and upload the .P12 OCES certificate

Add OCES certificate

It is subsequently possible to add a secondary certificate and to swap between the primary and secondary certificates.

Configuring NemLog-in 3 as Identity Provider (IdP)

You need to configure the OCES certificate before following this configuration.

1 - Start by creating an SAML 2.0 up-party in FoxIDs Control Client

  1. Select the Parties tab and then the Up-parties
  2. Click Create up-party and then SMAL 2.0
  3. Add the name
  4. Select show advanced settings
  5. Select the dot URL binding pattern
  6. Set the session lifetime to 1800 (30 minutes) in the Logout session tab
  7. Go back to the SAML tab

NemLog-in SAML 2.0 up-party

  1. Disable automatic update
  2. Click Read metadata from file and select the NemLog-in IdP-metadata

NemLog-in SAML 2.0 up-party

  1. Configure a custom SP issuer, the issuer is required to start with https://saml.
    • The issuer in this example https://saml.foxids.com/test-corp/nemlogin-test/
  2. Remove the * and configure claims, the following claims is most often used:
    • https://data.gov.dk/concept/core/nsis/loa
    • https://data.gov.dk/model/core/eid/cprUuid
    • https://data.gov.dk/model/core/eid/email
    • https://data.gov.dk/model/core/eid/firstName
    • https://data.gov.dk/model/core/eid/lastName
    • https://data.gov.dk/model/core/eid/professional/cvr
    • https://data.gov.dk/model/core/eid/professional/orgName
    • https://data.gov.dk/model/core/eid/professional/rid
    • https://data.gov.dk/model/core/specVersion

NemLog-in SAML 2.0 up-party

  1. In production only! Set certificate validation mode to Chain trust and revocation mode to Online
  2. Select to include the encryption certificate in metadata
  3. Set the NameID format in metadata to urn:oasis:names:tc:SAML:2.0:nameid-format:persistent

NemLog-in SAML 2.0 up-party

  1. Add an attribute consuming service in metadata and add the service name.
  2. Add all the claims configured in step 11 as requested attributes with the format urn:oasis:names:tc:SAML:2.0:attrname-format:uri. Optionally set each attribute as required.

NemLog-in SAML 2.0 up-party

  1. Add at least one technical contact person

NemLog-in SAML 2.0 up-party

  1. Click create
  2. Go to the top of the SAML 2.0 up-party
  3. Download the SAML 2.0 up-party SP-metadata, in this case https://foxids.com/test-corp/nemlogin-test/.nemlogin./saml/spmetadata.
  4. The SP-metadata file is used to configure the NemLog-in IT system.

2 - Then go to the NemLog-in adminstration protal

You need to create an NemLog-in IT-system or have someone else creating an NemLog-in IT-system and assign you access.

  1. Select the IT-system
  2. Click upload metadata file and upload the SAML 2.0 up-party SP-metadata file
  3. Go back to the IT-system
  4. Click the button Save the technical details
  5. Click Provision to integrationtest and then click Apply for integration test

3 - Add SAML 2.0 claim to JWT claim mappings in FoxIDs Control Client

FoxIDs internally converts SAML 2.0 clams to JWT claims. NemLog-in / OIOSAML 3 defines a set of SAML 2.0 claims where JWT mappings need to be added.

  1. Go to Settings tab and Claim mappings
  2. Add mappings for all the claims configured in step 1.11, you can create you own short JWT claim names if no standard name exist
  3. Click update

Claim mappings

You are done. The SAML 2.0 up-party can now be used as an up-party for down-parties in the track.

A down-party will only issue added claims.
Therefor, remember to add the JWT claims to OpenID Connect down-parties.

See Consider separate track on how to connect the NemLog-in track.

Logging

NemLog-in requires requests and responses to be logged including the signature proof and stored for half a year (180 days). It is also required to log which identity have done login and logout of which session, at what time and the IP address.
FoxIDs default log errors and events including the time and the IP address.

FoxIDs.com stores log data between 90 days to 180 days depending on the selected plan.

It can be configured which logs should be logged to the Application Insights which is part of the FoxIDs installation or to an external repository with a log stream.

The log level NemLog-in require is configured in the FoxIDs log settings:

  1. Enable log info trace
  2. Enable log claims trace
  3. Enable log message trace
  4. Click update

NemLog-in SAML 2.0 up-party

Request authentication context

You can request a desired NSIS assurance level as an authn context class reference.

NSIS assurance level in SAML 2.0 up-party

Possible NSIS assurance levels:

  • https://data.gov.dk/concept/core/nsis/loa/Low
  • https://data.gov.dk/concept/core/nsis/loa/Substantial
  • https://data.gov.dk/concept/core/nsis/loa/High

You can likewise specify ID type as an authn context class reference.

ID type in SAML 2.0 up-party

Possible ID types:

  • https://data.gov.dk/eid/Person
  • https://data.gov.dk/eid/Professional

And possible credential types:

  • https://nemlogin.dk/internal/credential/type/nemidkeycard
  • https://nemlogin.dk/internal/credential/type/nemidkeyfile
  • https://nemlogin.dk/internal/credential/type/mitid
  • https://nemlogin.dk/internal/credential/type/local
  • https://nemlogin.dk/internal/credential/type/test

In the case you need to provide different sets of authn context class references. You need to create multiple SAML 2.0 up-parties connected to NemLog-in as different IT systems.
E.g., if you need to support step-up authentication. Then you would create one SAML 2.0 up-party with authn context class reference https://data.gov.dk/concept/core/nsis/loa/Substantial and another SAML 2.0 up-party with authn context class reference https://data.gov.dk/concept/core/nsis/loa/High.