Skip to main content

Dropbox SAML integration

Multi-Factor Authentication (MFA) is an extra layer of security used when logging into websites or apps. Individuals are authenticated through more than one required security and validation procedure that only they know or have access to.

Security Assertion Markup Language (SAML) is a protocol for authenticating to web applications. SAML allows federated apps and organizations to communicate and trust one another’s users.

Arculix by SecureAuth, as a SAML provider, improves the user login experience for Dropbox users with convenient MFA, and offers a simple SAML solution for adding MFA and single sign-on (SSO) on Dropbox.


  • Configured Arculix instance and user account with administrative privileges for Arculix.

  • Configured Arculix LDAP Agent.

    For more information, see the Arculix LDAP Agent deployment guide.

  • User account with administrative privileges (Team Admin) for the Dropbox panel.

Dropbox configuration

In this section, you'll configure Dropbox as a service provider (SP).

  1. Download the SAML metadata and certificate for your organization from Arculix.

    Metadata download:<myorganization>/saml/download/metadata

    View metadata:<myorganization>/saml/metadata

    Certificate download:<myorganization>/saml/download/cert

  2. Log in to your Dropbox and enter your username and password.

  3. Go to Admin Console > Settings and choose Single Sign-on under Authentication.

  4. Set Single sign-on to optional or required.

  5. Enter the Sign-in URL you got earlier from Arculix.

  6. Click the certificate button. Upload the X.509 certificate file downloaded from Arculix

  7. Click Copy link and send it to your users for SSO login.


Arculix SAML configuration as an Identity Provider (IdP)

In this section, you'll add an application for Dropbox and set the SAML configuration settings. This will be the Identity Provider (IdP) side of the configuration.

  1. Log in to Arculix with an administrative account and go to Applications.

  2. Click Create New Application.

    Create new application
  3. In the New Application form, on the General tab, set the following configurations:


    Set the name of the application. This is the name to display for push notifications, in the Admin panel, Application portal, and audit logs.

    For example, Dropbox.


    Set to SAML Service Provider.

    Out of Band Methods 

    Select the allowed methods end users can choose to approve MFA requests.

    For example, Arculix Mobile app (push notifications), SMS, or Security Key.

    Message for MFA Requests 

    Optional. Type a message displayed to end users when sending an MFA request via push notification, SMS, or email.

  4. Select the SAML Service Provider Configuration tab, and set the following configurations:

    Issuer or Entity ID 

    Enter the Issuer/Entity ID of the SAML application.

    By default, it should be Dropbox.

    Log in URL 

    Enter the URL used by users to access Dropbox.

    Metadata URL

    Enter the URL containing metadata about your Dropbox.

    NameID Format 

    Set to Email Address.

    Dropbox requires that the NameID contains the user's email address.

    Name Identifier 

    Set to Email.

    ACS URL 

    Enter the Dropbox post-back URL.

    For example,

  5. Save your changes.

Test your application integration

  1. Go to the Dropbox SSO link you received from the first section.

  2. You will be redirected to the Arculix SSO page.

    Application login page with email
  3. After successful authentication, select your preferred MFA method to approve access to the Dropbox application.

    Select MFA method
  4. You are now authenticated with Arculix SSO-MFA and will be redirected to your Dropbox page.


If you have questions or need assistance, contact SecureAuth Support.


Want to learn more about our MFA solutions? Contact our Professional Services for a demo today.


All product names, trademarks, and registered trademarks are the property of their respective owners.

All company, product, and service names used in this document are for identification purposes only. The use of these names, trademarks, and brands do not constitute an endorsement by the SecureAuth Corporation.