Dashlane uses a SCIM API for managing users. In order to ensure the integrity of your Dashlane encryption keys, you must configure a Dashlane Encryption service running on your own infrastructure. Dashlane lets you configure this very easily on AWS or Azure. Running AWS or Azure services comes with a small additional cost from Amazon or Microsoft.

You should read the background Dashlane documentation carefully and work through the specifics on self-hosted SSO.

You cannot currently use Dashlane Confidential SSO with SCIM.

Also, at present, you cannot swap between Confidential SSO and Self-hosted SSO. This may change in future so please check by going to the Admin console > Settings > Single sign-on.

Set up the encryption service (self-hosted SSO)

  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.

Was this article helpful?

0 out of 0 found this helpful



Please sign in to leave a comment.