Configuring Dataedo with Duo

This guide walks you through setting up Dataedo to work with a SAML identity provider. We'll use Duo as an example, but the steps are similar for other providers.

Initial configuration in Duo Admin Portal

caution

Before proceeding, ensure your organization has Duo Single Sign-On (SSO) configured. For setup instructions, see the documentation: How to Use Duo Single Sign-On (SSO).

1. Open the Duo Admin Portal.

2. Select Applications and click Protect an Application.

   

3. In the filter box, type "Generic SAML" and click Protect next to Generic SAML Service Provider.

   

4. The Configuration page will appear. Under Basic Configuration, enter your Application name and choose the User Access settings according to your organization's security policy.

   

5. Proceed to the Metadata section. Copy the Metadata URL. You'll use this later.

   

6. Continue to the Service Provider section.

   • In the Metadata Discovery field select None (manual input).

   • In the Entity ID field, enter a unique identifier (e.g., the address of your Dataedo Portal). You'll use this value later.

   • In the Assertion Consumer Service (ACS) URL field, enter the Dataedo Portal URL followed by /api/api/auth/assertion-consumer.
     Example: https://your-dataedo-web.address/api/api/auth/assertion-consumer.

   

7. Click Save to apply your settings.

   

Configuring group roles in Duo (optional)

You can include group information in the SAML assertion by using role attributes. This allows you to map Duo groups to specific roles in Dataedo.

1. Scroll to the SAML Response section of your Duo application settings and expand the Role attributes panel.

2. Fill in the fields:

   • Attribute name: "Group"
   • Service Provider Role: type the role you want to assign (e.g., Editor)
   • Duo Groups: select the group whose members should receive that role
   
   
   

3. Make sure the appropriate users are members of the selected Duo group:

   • Navigate to Users > Groups
   • Confirm correct membership for each user

Test connection

When adding a SAML provider, you have the option to test it before saving it. Testing helps you check whether everything is set up correctly and prevent a situation where users cannot log in via SAML after you configure it. You can test it using the Test SAML authentication button.

You can also test existing SAML configurations. To do so, click the three dots next to an authentication method you want to test and select Test SAML authentication.

No matter which option you choose, you will then see a popup with a Dataedo log-in page. You should log-in using SAML. After this log-in, you will see a screen with the results of the test.

The checks are as follows:

• Provider connection — if it passes, it means that the metadata you provided is correct, and a SAML sign-in request could be created.
• Sign in at the Identity Provider — a success means that Portal was able to successfully authenticate using your credentials. If it fails, it probably means that you do not have the necessary permissions in the Identity Provider.
• Returned to the application — if it passes, it means that a return address is correctly configured. This step can return errors if you close the popup window before all the checks can run
• Response valid — this checks whether the connection was secure.

The remaining two checks are not a pass/fail check; instead, they return warnings regarding easy-to-overlook details. If you see a warning, analyze it carefully to make sure that the outcome is what you intended. If not, make sure to fix the issues within your Identity Provider.

User Access in Portal — this warning will show up when the email you used to check the SAML connection could successfully authenticate, but raised issues in Dataedo. The account (matched via NameId) might for example lack Admin rights, or exist in SAML but not have a corresponding Dataedo user. Groups — this warning shows up when a group that is configured in your Identity Provider is not mapped to any Dataedo groups. This means that some intended permissions might not be automatically assigned to users, e.g., a Stewards group in your Identity Provider is meant for Data Stewards, but is not mapped to any Dataedo group carrying the corresponding permissions. Members of the Stewards group in your Identity Provider will not get the desired permissions.

At the bottom of the SAML test result page, you will see a SAML server response button. Clicking it will show a response, if you are encountering errors, you can copy the response and forward it to your organization's IT specialist.

Configuring SAML in Dataedo Portal UI (version 25.2+)

Starting with version 25.2, you can configure SAML identity providers directly in the Portal interface. You no longer need to edit appsettings.json. All settings are now stored in the database and are preserved during upgrades.

Step 1 – Open Login Options in System Settings

1. In the Portal, go to Settings > System Settings > Login options.
2. Expand the SSO Service (SAML) section.
3. Toggle Enable login method to activate SAML login. The toggle appears blue when active.

Step 2 – Add or Edit a SAML Identity Provider

1. Under Configured SAML providers, you will see a list of existing providers (if any).
2. To add a new one, click Add SAML.

3. Fill in the fields with values from your identity provider (for example, Entra ID):
   • Display name – for example, Azure_AD.
   • IdP Metadata – metadata URL or file path.
   • Issuer – from your provider's SAML configuration.
   • Signature algorithm – for example, http://www.w3.org/2001/04/xmldsig-more#rsa-sha256.
   • Certificate validation mode – for example, ChainTrust.

4. Click Save to store your provider configuration.

Step 3 – Test the Login Option

Once configured, the login screen will display an option to log in via the added SAML provider.

Clicking this will redirect the user to the identity provider login page. Upon successful authentication, users are redirected back to the Portal.

Synchronizing User Groups via SAML

warning

For this feature to work, you must configure group claims in Duo first

Dataedo Portal can automatically assign users to groups based on their group membership in the identity provider (such as Entra ID). This simplifies access management since group membership is maintained externally, and roles are assigned dynamically during login.

Step 1 – Enable Group Synchronization in Portal

warning

The Synchronize with SAML and Automatically assign group to each new user options cannot be simultaneously applied to the same user group. These two options directly contradict each other.

1. Navigate to User Management>Groups and either create a new group or open an existing one.
2. In the Settings tab:
   • Enable Synchronize with SAML [1]
   • Select the correct SAML provider from a drop down [2]
   • Enter the group name from your identity provider that should map to this Portal group [3]

Step 2 – Assign Roles to the Group

Open the group's Permissions tab and click Add Role

A popup will appear. You have to provide:

• The scope [1] — the scope defines where the role permissions will apply. Should this User Group have editor privileges in the entire repository or just select Domains or Data Sources?
• The role [2] — the type of role you want to give to this user group. Each role comes with different permissions.

After you define the role and its scope, save it using the Add [3] button.

Once this is set up, group membership changes in Entra ID (Azure ID) will automatically apply the correct roles the next time a user logs in.

Configuring SAML in Dataedo Portal Docker image

1. Open the .env file (located in the same folder as docker-compose.yml) and find the Single Sign-On section:

   # Single Sign On Configuration
   # Add the following settings to your environment file.
   
   # Paste the Metadata URL copied from Duo Admin Portal or the file path to the metadata XML.
   # Example: https://sso-a06d2d5e.sso.duosecurity.com/saml2/sp/DI7SDPCIHNSN9MOYP7QK/metadata
   DATAEDO_SSO_IDP_METADATA="https://sso-a06d2d5e.sso.duosecurity.com/saml2/sp/DI7SDPCIHNSN9MOYP7QK/metadata"
   
   # Enter the Entity ID configured in Duo Admin Portal.
   # Example: Dataedo_PT_VM
   DATAEDO_SSO_ISSUER="Dataedo_PT_VM"
   
   # Default: RSA_SHA256. Change if using another signature algorithm.
   # For RSA_SHA1, use http://www.w3.org/2001/04/xmldsig-more#rsa-sha1
   DATAEDO_SSO_SIGNATURE_ALGORITHM=http://www.w3.org/2001/04/xmldsig-more#rsa-sha256
   
   # Certificate validation mode. Default is ChainTrust.
   DATAEDO_SSO_CERTIFICATE_VALIDATION_MODE=ChainTrust
   
   # Revocation mode. Default is NoCheck.
   DATAEDO_SSO_REVOCATION_MODE=NoCheck
   
   # Enter the display name shown during login.
   # Example: Duo_Security (no blank spaces, use underscores if needed)
   DATAEDO_SSO_DISPLAY_NAME="Duo_Security"
   
   # Enter your Dataedo Portal address.
   # Example: https://yourwebsite.com/
   DATAEDO_SSO_CLIENT_URL="https://yourwebsite.com/"
   

2. Save the .env file and restart the Docker containers by running the following command:

   docker-compose down && docker-compose up -d

Testing the SAML integration

1. Open the Dataedo Portal login page in your browser.
2. You'll see the option to log in with your configured SAML provider (Duo Security).
3. Log in using a user account managed by your Duo configuration.
4. Verify successful login and access to the Dataedo Portal.

With these steps, you've successfully configured Duo as a SAML Identity Provider for Dataedo!

Need help?

If you run into any problems or have questions, reach out to Dataedo support.