Setting Up SAML Single Sign-On (SSO) in LEM / BP

Modified on Fri, 30 Oct at 4:34 PM

Single sign-on (SSO) lets users log in to DiliTrust with their company account, through their company's own login service. This login service is called the identity provider (IdP). DiliTrust uses the SAML standard for SSO, and the login always starts from DiliTrust (this is called "Service Provider initiated").

This guide explains how to set up SAML SSO for a new customer in Legal Entity Management (LEM) and Board Portal (BP), and what users see once it is set up.


✋ Who can do what

  • The person setting up SSO collects the customer's information, fills in the SAML configuration and shares DiliTrust's metadata with the customer.
  • The customer's IT team provides the identity provider information and, for ADFS, checks the signature settings.
  • Users (administrators and board members) then log in through SSO in the same way.

✍ Person setting up SSO: collect the information

You need four pieces of information from the customer's identity provider:

  • EntityID
  • X509 certificate(s)
  • Login URL
  • Allowed domain name(s)

Option 1: import the metadata file (simplest)

  1. Ask the customer for their metadata.xml file.
  2. Upload it on the SAML client settings page. The EntityID, X509 certificate(s) and login URL are filled in automatically if the file contains them.
  3. If information is missing from the file, ask the customer for it.

Importing a new XML file replaces all existing client settings.

Option 2: enter the information manually

Open the customer's metadata.xml file and find:

  • the EntityID in the EntityDescriptor node;
  • the X509 certificate(s) in the X509Certificate node. There may be several: include them all;
  • the login URL in the SingleSignOnService node.

Line numbers vary from file to file, so always look for the node names.


✅ Person setting up SSO: fill in the SAML configuration

Open the SAML client configuration page.

  1. Tick Enable SAML for SSO integration.
  2. Choose how users log in:
    • Full SAML login (recommended): users log in only through SAML. Tick Force all users to login through SAML.
    • Partial SAML login: users can still log in with their email and password at the data center level.
  3. Check the authentication methods. Six are supported by default: Password, Password Protection Transport, TLS Client, X.509, Integrated Windows and Kerberos. For other methods, see the training material on non-standard authentication methods.
  4. Leave Strict protocol turned on (it is on by default). It checks the identity provider's information before processing it, for more security.
  5. In Client Settings, enter or check the Entity ID, the IdP login URL, the X509 certificate(s) and the exclusive domain name(s), separated by commas.
  6. Click Save. The customer's own metadata is generated.
  7. Copy this metadata and send it to the customer so they can validate and test the connection.

⚖️ Customer's IT team: extra step for ADFS

If the customer uses Windows Active Directory Federation Services (ADFS), both the message and the assertion must be signed. On the ADFS server, run:

Get-AdfsRelyingPartyTrust -Identifier <A_DILITRUST_APP_IDENTIFIER>

If SamlResponseSignature is not set to MessageAndAssertion, run:

Set-AdfsRelyingPartyTrust -TargetIdentifier "<A_DILITRUST_APP_IDENTIFIER>" -SamlResponseSignature "MessageAndAssertion"

Valid DiliTrust application identifiers: dilitrust_gov_eu, dilitrust_gov_na, dilitrust_exec_eu, dilitrust_exec_na, dilitrust_dataroom_prod_eu, dilitrust_dataroom_prod_na.


☝ Users: first login and password creation

Unless SAML login is forced, users are still asked to create a DiliTrust password when they activate their account. This is expected and cannot be skipped today, even if their email domain is in the exclusive domain names.

If a user enters their email address on https://auth.dilitrust.com/, they receive a password creation email. Its link opens the DiliTrust password creation page and never redirects to the identity provider.


⌚ Users: open a meeting link from a notification email

Board Portal notification emails can include a link to a meeting. With SSO turned on:

  1. The link opens the DiliTrust login page. The link does not identify the user, so they type their email address once.
  2. What happens next depends on the setting:
    • Forced SAML login (Force all users to login through SAML is ticked): the user is sent straight to their identity provider. Users who try to log in with a password are also sent there.
    • Optional SAML login (the option is not ticked): the user is not sent to the identity provider. They enter their DiliTrust password, plus two-factor authentication if it is set up.
  3. After logging in, the user lands directly on the meeting, in both cases.

Good to know

  • Redirection to the identity provider only happens when SAML login is forced.
  • Forced SAML login applies to the user's whole account. If a user belongs to several customers, it is forced as soon as one of them forces it.
  • Some users do not land on the meeting right away: users with terms of use to accept see that page first, support users go to the support dashboard, and users who are not members of any group are not redirected to the meeting.
  • A valid meeting link contains the meeting ID and the group ID: /fr/redirection_email/meeting/{meeting_id}/{group_id}. Without the group ID, the user sees a "page not found" error (404).

❗ Limitations and troubleshooting

  • A SAML configuration for a group cannot use the same email domain as the client configuration. Each email domain can exist only once per configuration.
  • If the customer has connection problems during testing, especially with Microsoft identity providers using biometric or hardware authentication, see the training material on non-standard authentication methods. Always confirm with R&D before turning on non-standard options.

❓ FAQ

Why are SSO users asked to create a password?

Unless SAML login is forced, password creation is part of account activation and cannot be skipped today.

Why does a meeting link show a 404 error?

The link is missing the group ID. A valid link contains both the meeting ID and the group ID.

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article