You can integrate Dashlane with your Identity Provider (IdP) using the Dashlane SCIM Provisioning for plan members.
Prerequisites
To complete this setup, you need:
- Admin access to the Dashlane Admin Console
- Admin access to your organization’s Identity Provider
- Confidential SSO or self-hosted SSO turned on for your plan members
Set up User SCIM Provisioning
Set up SCIM Provisioning with Confidential SSO
If you have one Azure, Okta, or PingID as your Identity Provider, follow the specific steps under Set up SCIM Provisioning.
Step 1: Generate SCIM API Token in Dashlane
- Log in to the Admin Console.
- In the Integrations section, select Provisioning and then Confidential Provisioning.
-
Select Set up or Edit if you've already started the setup.
If this option is greyed out and unavailable, you might need to set up Confidential SSO first. If you've previously set up AD sync, you need to stop the on-prem AD sync script in PowerShell and turn off AD sync in the Admin Console.
Set up Confidential SSO and SCIM Provisioning - Log out of Dashlane and log back in to update the provisioning options. If SSO is turned on and Confidential Provisioning is still greyed out, select Chat with bot in the bottom right of this page to contact our Support team.
- In Provisioning and in Step 1: Generate SCIM API token, select Generate Token.
- Copy the SCIM API token in Step 2: Copy token.
- Turn on the toggle for Step 3: Activate automatic user provisioning.
Step 2: Configure SCIM API Token in your Identity Provider
- In the SSO app of your Identity Provider, go to the User Provisioning page.
- Copy the SCIM Endpoint from the Dashlane Admin Console and enter the value under the SCIM URL field in your Identity Provider.
- Enter the SCIM API token copied from the Dashlane Admin Console in the SCIM API token field in your Identity Provider.
- Ensure you select the Bearer Token option.
- Turn on user provisioning.
- Turn off group provisioning via SCIM, as sharing group creation isn’t supported by the Confidential SCIM protocol.
- In case you also turn on group provisioning via SAML, ensure that all groups have the exact same name, capitalization, and spacing as in your AD sync groups to prevent sync issues.
- Assign the users and/or user groups to your SSO app to sync.
- Test the connection to verify it works.
Check your Identity Provider documentation for any limitations and additional information.
Set up SCIM Provisioning with self-hosted SSO
If you have Azure, Okta, or JumpCloud as your Identity Provider, select which one and follow the specific steps under Set up SCIM Provisioning.
Step 1: Generate SCIM API Token in Dashlane
- Log in to the Admin Console.
- In the Integrations section, select Provisioning and then Self-hosted Provisioning.
-
In SCIM Provisioning settings, select Set up or Edit if you've already started the setup.
If this option is greyed out and unavailable, and you've previously set up AD sync, you need to stop the on-prem AD sync script in PowerShell and turn off AD sync in the Admin Console.
- Log out of Dashlane and log back in to update the Provisioning options. If SSO is turned on and self-hosted Provisioning is still greyed out, select Chat with bot in the bottom right of this page to contact our Support team.
- In SCIM provisioning settings and in SCIM API token, select Generate Token.
- Copy the SCIM API token.
- Turn on the toggle for Allow the encryption service to sync directory, then select Save changes.
-
Restart your encryption service.
Step 2: Configure SCIM API Token in your Identity Provider
- In your Identity Provider, go to the User Provisioning page
- Copy the SCIM Endpoint from the Dashlane Admin Console and enter the value under the SCIM URL field in your Identity Provider.
- Enter the SCIM API token copied from the Dashlane Admin Console in the SCIM API token field in your Identity Provider.
- Ensure you select the Bearer Token option.
- Turn on user provisioning and group provisioning.
- Assign the users and/or user groups to your SSO app to sync. Ensure that all groups have the exact same name, capitalization, and spacing as in your AD sync groups to prevent sync issues.
- Test the connection to verify it works.
Check your Identity Provider documentation for any limitations and additional information.