Dashlane

Dashlane uses a SCIM API for managing users. 

You should read the background Dashlane documentation carefully and work through whether you are using Self-hosted SSO or Confidential SSO. Historically Confidential SSO did not support SCIM (which Trelica requires), but Dashlane now supports both with SCIM.

To enable SSO go to the Admin console > Integrations > Single sign-on.

Enabling SCIM for Confidential Provisioning

First configure SSO. Then go to Integrations > Provisioning and click Set up under Confidential Provisioning:

Copy and paste the SCIM API token and SCIM Endpoint to Trelica.

Make sure you Activate automatic user provisioning.

Setting up a Dashlane self-hosted SSO encryption service

1. Choose where you will deploy the service - in this example we will use Azure, then name your service endpoint (e.g. yourorg-sso) and click Generate and save for the configuration. 
   
2. Copy the configuration data to the clipboard and choose Go to service host:
3. You will then be prompted to login to Azure. Click Edit parameters.
4. Paste in your Configuration data and click Save.
5. Finally choose a Resource group to add the services to:
   
6. Click Continue to validate the configuration, and then click Create:
   
7. Back in Dashlane validate that the Encryption service is running correctly. Then click Set up under SCIM provisioning settings:
   
8. Click Generate token and then cut and paste the token and the SCIM endpoint into Trelica.
9. You will also need to enable Allow the encryption service to sync directory.
10. Click Save changes.