Integrating JumpCloud SAML SSO with Dialpad

Prev Next

Use JumpCloud SAML Single Sign On (SSO) to give Dialpad users convenient and secure access with a single set of credentials. 

Let's dive into the details.

Who can use this
The JumpCloud SAML integration is available to Dialpad ConnectDialpad Sell, and Dialpad Support users on a Premium plan. 

Enable SAML in Dialpad

First things first, you'll need to enable SAML in Dialpad.

Head to your Admin Settings from Dialpad.com 

  1. Select My Company 
  2. Select Authentication
  3. Select SAML
  4. Navigate to Choose your provider 
  5. Select Custom
  6. Take note of the values for SP SSO Url (ACS) and SP Entity ID
    1. The values will differ based on the domain identifier of your company.
    2. Keep this tab open — we'll revisit this page after configuring SAML on JumpCloud.

Configure SAML SSO in JumpCloud

Next, its time to configure SAML SSO in Jumpcloud.

  1. Login to JumpCloud as an admin
  2. Select SSO 
  3. Select the + icon to add a new application
  4. Type Dialpad in the search bar
  5. Select Configure
    image13.png
  6. Enter a Display Label
  7. Select Activate
  8. Select Continue 
    image7.png
  9. Select on the created application 
    image2.png
  10. Navigate to the SSO tab 
  11. Update the SP Entity ID and ACS URL attributes with the values obtained from the Dialpad SAML configuration 

    JumpCloud attribute to populate

    Attribute name in Dialpad

    Example Value

    SP Entity ID

    SP Entity ID

    https://dialpad.com/api/saml/metadata/custom/aerolabs.io

    ACS URL

    SP SSO Url (ACS)

    https://dialpad.com/saml/sso/custom/aerolabs.io

  12. Select Save
  13. Select the created application again to continue
  14. Navigate to the Attributes section within the SSO tab
  15. Verify the email under Service Provider Attribute Name
  16. Select the created application again to continue 
  17. Under the SSO tab, you’ll need the following attributes (found in the table) from JumpCloud. 
    1. The values against these attributes shall be configured back in the Dialpad SAML configuration tab.
Tip
The email under Service Provider Attribute Name should be mapped to the JumpCloud attribute name email.

Dialpad Attribute to populate

JumpCloud attribute to use

Example value

IdP Entity ID (Issuer)

IdP Entity ID

JumpCloud

IdP SSO URL

IDP URL

https://sso.jumpcloud.com/saml2/dialpad

Certificate

IDP Certificate*

Downloaded pem file (without the BEGIN and END tags)

* The IDP certificate can be downloaded in JumpCloud.

image8.png

Configure SAML in Dialpad

Now, it's time to populate the IdP attributes in Dialpad. 

Head to your Admin Settings from Dialpad.com 

  1. Select My Company 
  2. Select Authentication
  3. Select SAML
  4. Populate the IdP related attributes retrieved from the previous section (IdP Entity ID, IdP SSO URL and Certificate)
  5. Select Save

Setting up SAML users 

Now that SSO has been configured, its time to set up the users. 

  1. Login as an administrator in JumpCloud
  2. Select User Groups
  3. Select a group
  4. Navigate to the Applications tab
  5. Select the Dialpad SSO application
     image4.png
  6. Log in to JumpCloud using a non-admin test account (picked from the above group) using another browser profile/session 
    1. The Dialpad application should be listed under Applications
      image12.png
  7. Using the same test user’s browser session, navigate to Dialpad Login in a different tab 
  8. Select Login with Another Provider


    image6.png
  9. Enter the domain of the user
  10. Select Next

After a few redirections, the user should now be logged in to Dialpad.

Enforcing SAML-based SSO 

Add an extra level of security by blocking your users from using other SSO providers when logging into Dialpad. 

To restrict the use of other authentication providers, navigate to your Admin Settings at Dialpad.com

  1. Select My Companyenforce-saml
  2. Select Authentication
  3. Select SAML
  4. Select Prevent users from logging in with other SSO providersenforce-sso
  5. Select Save 

Once saved, your users won't be able to use Microsoft and Google SSO (or even their username and password) to log in to Dialpad.