Skip to main content
Druva Documentation

Set up single sign-on (SSO)

Single sign-on (SSO) is a mechanism that allows users to access multiple resources using a single action of authentication and authorization. Druva supports SSO for administrators. By enabling SSO, administrators can access all Druva services without the need for a separate login. An SSO login validates usernames and passwords against your corporate user database, typically managed by your Identity Provider (IdP). A successful validation ensures that users and administrators can log on to Druva Cloud Platform Console, without the need for a Druva generated password. 

 

 

  • Only a Druva Cloud administrator can set up Single Sign-on. 
  • Configure Single Sign-on based on the applicable scenarios:
    • New Druva customers that is; Phoenix customers on-boarded after 02 July 2018 and inSync customers on-boarded after 14 July 2018 must refer to the instructions given in this article. 
    • Existing Phoenix and inSync customers who already have configured Single Sign-on, must continue to use the existing Single Sign-on settings of Phoenix and the Single Sign-on settings of inSync as applicable.

 

How SSO works

Druva supports Single sign-on by implementing federated authentication using Security Assertion Markup Language (SAML) version 2.0. Federated authentication allows Druva to skip validation of passwords. 

To enable SSO, an administrator must first work with an Identity Provider (IdP) to create a corporate database that includes all Druva administrators. If you already have an IdP, you can configure Druva to work with this IdP. The IdP maintains a record of all usernames and their subsequent passwords in an encrypted format.

If you created a corporate database with an IdP for the first time, administrators logging on for the first time are redirected to an IdP login details page that prompts the user for a one-time provision of passwords.  The IdP redirects the user to the Druva Cloud Platform Console.  The administrators can now access the Druva Cloud Platform Console without individual passwords.

However, if you use a preconfigured IdP or if this is a subsequent login, Druva uses SAML assertions in an HTTP POST profile to communicate with your IdP. For every login attempt, Druva sends SAML requests to the IdP login URL specified under account icon > Settings > Single Sign-On > Edit. The IdP validates the SAML query, sets assertion in HTTP POST to True, and sends this response to Druva. Druva receives the assertion, which indicates that the administrator is validated, and allowed access to Druva Cloud Platform Console.

However, if the IdP does not find a match within its database, it sets assertion in HTTP POST to False, thus indicating that the administrator is not authorized to access Druva Cloud Platform Console. Upon receiving this response, Druva denies access to Druva Cloud Platform Console.

Supported Identity Providers (IdPs) 

Druva integrates with the majority of the SAML IdPs. This section provides information on the SAML IdPs that Druva certifies and supports.

Support Levels Definition

Druva categorizes its IdP support levels as follows:

  • Certified IdPs - A certified IdP is fully tested by Druva Quality Assurance (QA) team. Druva certifies these IdPs and performs regular testing with every cloud release to ensure the SSO functionality works as expected.
  • Supported IdPs - A supported IdP is not tested by the Druva QA team with every cloud release, however, the SSO functionality should work as expected. Druva will provide support for such IdPs. Issues that require time and resources beyond commercial viability may not be addressed.

Certified IdPs

  • Okta
  • PingOne
  • Active Directory Federation Services (ADFS)
    • Windows Server 2012 R2 (64-bit) is certified to work with ADFS 3.0
    • Windows Server 2008 R2 (64-bit) is certified to work with ADFS 2.0

Supported IdPs

  • All IdPs that support SAML 2.0.
Note: Contact Druva Support for assistance to configure a IdP that is not listed under Certified IdPs.

SSO configuration workflow

This table describes the chronology that you should follow for enabling SSO for the administrator and user access. 

Task Number Task Description

1

Work with your IdP

Before you enable SSO, you must first set up a corporate database with an Identity Provider (IdP). If your organization is using an IdP, you must work with your IdP to get details such as IdP URL and IdP certificate. 

Druva supports leading IdPs such as Okta, PingIdentity, OneLogin, and Active Directory Federation Services (ADFS).

2

 

Configure Druva for Single sign-on  

To enable SSO access for users and administrators you must configure Druva to recognize IdP details that you obtained when you performed Task 1. 

After you configure Druva for Single sign-on, the Druva Cloud Platform Console provides an option to generate SSO Token. To allow your IdP to recognize requests that Druva sends, you must first generate an SSO token, and then update your IdP configuration with this token. The SSO token uniquely identifies Druva login requests. For login attempts, Druva sends a request to the IdP (typically using HTTP POST). In its response, the IdP attaches this token, thereby indicating the validity of authentication requests. When Druva receives this response, it uses the SSO token ID to validate the authenticity of the IdP response.

3 Update IdP details To provide the authentication token to your IdP, you must update your IdP configuration to include this token. 

For greater understanding, share this handy article describing the SSO workflow with your administrator

Work with your IdP

To enable SSO for users and administrators in your organization, you must work with your Identity Provider (IdP) to create a corporate database that contains usernames and passwords of Druva administrators. If your organization is using an IdP, you can configure Druva to recognize this IdP. The IdP maintains a record of credentials and validates a username against its password for each login attempt. Druva supports leading IdPs such as Okta, PingIdentity, OneLogin, and Active Directory Federation Services (ADFS).

Obtain IdP details

To configure Druva for SSO, you must obtain the following information from your IdP. 

  • ID Provider Login URL
  • ID Provider Certificate

Configure Druva for Single sign-on

If you are a Druva Cloud administrator, you can configure SSO for your Druva account. At the time of configuration, you must provide IdP details that you obtained at the time of working with your IdP.

To configure single sign-on settings

  1. On the Druva Cloud Platform Console, click the account icon > Settings.
    reach-settings.png
  2. In the settings page, in the Single Sign-On row, click Edit. The Edit Single Sign-On Settings window appears.
  3. Provide the appropriate information for each field.
    Field Action

    ID Provider Login URL

    Type the identity provider's URL.  The URL that you provide in this field points to the identity provider's authentication page. 

    When the email is entered on the Druva Cloud Platform Console login page, the administrator is directed to the identity provider's authentication page.

    ID Provider Certificate

    Copy the content of the public key certificate that your IdP provided. This certificate ensures that the communication between Druva and your IdP is secure. 

    AuthnRequests Signed

    Select this checkbox if you want to sign SAML Authentication Requests.

    By default, SAML Authentication Requests are not signed.

    Encrypt Assertions

    Select this checkbox, if you want to enable encryption for the SAML assertions.

    By default, encryption is disabled.

    Single Sign-On for Administrators Enable the Administrators log into Druva Cloud through SSO provider setting to let administrators use the SSO configuration to log in to Druva Cloud Platform Console and use Druva services. 
    Failsafe for Administrators Enable the Failsafe for Administrators setting to provide Druva Cloud administrators an option to use a password to log in to Druva Cloud Platform Console even if SSO is enabled for administrators.

    Only Druva Cloud administrators get the privilege to use a password to log in to Druva Cloud Platform Console.

    By default, this setting is enabled, and Druva recommends that you DO NOT disable this setting. 
    Single Sign-On for inSync End Users To let inSync end users log in using SSO configuration, enable the setting through the general section of their profile. For more information, see Enable SSO for inSync users.
  4. Click Save
  5. After the configuration is complete, you can see the Generate SSO Token button. Click this button to generate an SSO token for your IdP and click the Copy button to copy the token on your clipboard. Save it as plain text using a text editor for later use. 

Update IdP details

To allow your IdP to recognize requests that Druva sends, update your IdP configuration with the token you generated in step 5 above. The SSO token uniquely identifies Druva login requests. For login attempts, Druva sends a request to the IdP (typically using HTTP POST). In its response, the IdP attaches this token, thereby indicating the veracity of authentication requests. When Druva receives this response, it uses the SSO token ID to validate the authenticity of the IdP response.

Before updating IdP details, ensure that:

  • You have the SAML_Identifier/entity ID parameter handy. 
  • You have access to the documentation for the Identity Provider that you are using. This article contains instructions that serve as a guide, and not as exact tasks that you must perform.

Unless otherwise noted, use the following procedure as a guide. Use the documentation provided by your IdP for the correct configuration procedure.

To update IdP details

  1. Log on to the IdP administrator console with elevated rights.  
    For example, the Global Administrator role supported by PingOne provides full access to manage and control all aspects of the administrator console. 
  2. Create a SAML application. 
  3. Provide the Assertion Consumer Service URL or the SSO URL.
    The Assertion Consumer Service is a SAML-compliant URL that is hosted on your IdP. It acts as a receptor for form submissions and page redirects. The Assertion service URL or the SSO URL for the Druva Cloud Platform Console is:  https://login.druva.com/api/commonlogin/samlconsume 
  4. Provide the SAML_Identifier value as the entity ID. In Okta, this is the Audience URI field. In this field, provide: 
    • DCP-login for public cloud
    • DCP-govlogin for govcloud
    Note: This value is case sensitive.
  5. In the Name ID format field, select EmailAddress.
  6. Leave the Default RelayState field blank.  
  7. If the identity provider requires an application URL, enter: https://login.druva.com for Druva Cloud Platform Console.
  8. Provide the Name ID Format, SSO token, and other details that your IdP mandates. For Okta, 
    • In the  SSO token section, enter the name as druva_auth_token
    • In the value field, paste the SSO token that you generated in step 5 of the procedure above
  9. Save your changes. 

The Single Sign-on is set up after all the steps are completed successfully, and administrators can log in to the Druva Cloud Platform Console by using SSO in your organization. 

Key points

Following things happen after you set up SSO:

  • Failsafe admins (Druva Cloud administrators) receive an email with a password when Single sign-on is enabled. 
  • The password is reset for all administrators when Single sign-on is disabled. 
  • Password policy is enabled for Druva Cloud administrators when Single sign-on is enabled. After a Druva Cloud administrators logs in using Single sign-on, the Druva Cloud Platform Console prompts the administrator to reset the password. 
  • Administrators are not notified if the Failsafe for Administrators setting is disabled.