Articles in this section

OneLogin + Dialpad

Margaret Beinarovics
Updated

Your IT team should be doing more than managing lost passwords. With Dialpad's OneLogin’s single sign-on (SSO) integration, IT teams never have to worry about users managing multiple passwords or usernames — everything is synced to their OneLogin account. Users simply log into OneLogin and select Dialpad from their app panel to log in and start placing calls.

Let's go over this integration.

Who can use this

Dialpad's OneLogin integration  is available to eligible Dialpad Sell, Dialpad Support, and Dialpad Connect users. Refer to our Pricing Page to see if you have access to this feature. If you have questions about your plan, reach out to your Customer Success Manager or Dialpad Customer Care. Admins can manage users via the OneLogin Administrative Portal. 

Create API key

First things first, you'll need your Company Admin to set up API keys. 

Have your Company Admin navigate to their Dialpad Admin Settings.

  1. Navigate to My Company
  2. Select Authentication 
  3. Select API Keys
  4. Select Add Key and generate a new API key for OneLogin
    Screenshot of the Dialpad API Keys dashboard featuring an orange box around the 'Authentication' navigation menu and an orange arrow pointing to a highlighted '+ Add key' button in the upper right.
  5. Copy the API key

Configure OneLogin

Before you start configuring OneLogin, make sure you have:

  • Dialpad Company Admin (Super Admin) access
  • OneLogin Administrative Portal Access
  • Available licenses 

In the OneLogin administrative portal, head to the Applications tab.

  1. Select Add App (in the upper-right corner)
    Screenshot of the OneLogin Applications portal header displaying navigation tabs and top-right action buttons for 'Download JSON' and 'Add App'.
  2. Type Dialpad in the Search bar
    Screenshot of the OneLogin 'Find Applications' search page displaying 'Dialpad' entered into the search field and showing the Dialpad application result supporting SAML 2.0 and provisioning.
  3. Select Dialpad (with SAML 2.0 and provisioning tabs

  4. Enter a Display Name
    Screenshot of the 'Add Dialpad' app configuration page in OneLogin showing 'Dialpad' entered into the Display Name field, with a blue 'Save' button in the upper right corner.

     

    Tip

    Before moving to the configuration tab in OneLogin, open the SAML settings on the Dialpad Admin page in another browser tab.

  5. Select Save
  6. Select OneLogin as the SAML provider
    Screenshot of the Dialpad SAML Configuration page, featuring an orange box and arrow pointing to the provider dropdown menu with 'OneLogin' highlighted.
  7. Take note of the SP SSO Url and SP Entity ID
    Screenshot of the Dialpad SAML Configuration page, featuring an orange box highlighting the generated 'SP SSO Url (ACS)' and 'SP Entity ID' field values above empty Identity Provider input fields.
  8. Navigate to the Configuration tab of the Dialpad app in OneLogin Admin portal
  9. Enter your org domain in Application Details 
    • It must match the SP SSO Url
      Screenshot of the API Connection configuration settings showing a red Disabled API Status alongside an Enable button, with a string entered into the SCIM Bearer Token input field.
  10. In API Connection, enter the API key previously generated in the SCIM Bearer Token field.
    Screenshot of the API Connection interface displaying a green Enabled API Status with a Disable button, alongside a populated SCIM Bearer Token field.
  11. Select Enable 
  12. Select Save

  13. Click the SSO OneLogin, while keeping the Dialpad SAML page open in another tab

    Screenshot of the Dialpad Application details page in OneLogin under the Configuration tab, displaying a populated Dialpad Domain field with a sidebar menu highlighting the SSO tab option on the left.

  14. Copy and paste the following OneLogin attributes into their corresponding Dialpad fields as specified in the table below
    Screenshot of a mapping guide for OneLogin SAML 2.0 configuration, showing an attribute mapping table alongside a side-by-side view with blue arrows mapping values from OneLogin to the corresponding fields in Dialpad.
  15. Select Save on the Dialpad page

Configure user provisioning

Now that SAML has been set up, you'll need to configure your User provisioning. 

  1. Navigate to the Provisioning tab 
  2. Check "Enable Provisioning" to set up SCIM 
  3. Select Save

Note

Requiring Admin approval for creating, deleting, and updating requires each change to be approved again.

Creating and deleting Dialpad users

Once OneLogin is configured for SCIM, new Users can be provisioned on Dialpad by creating them in the OneLogin portal. 

  1. Navigate to the Users tab
  2. Select New User
  3. Create the new User
    Screenshot of the OneLogin New User creation form displaying populated fields for First Name, Last Name, Email, and Username, with a dark blue 'Save User' button in the upper right corner.
  4. Select Save User    

Next, navigate to Applications  and select Add the Dialpad Application login 

Update any relevant details and hit Save. 

Screenshot of the 'Edit Dialpad Public Login' configuration window showing populated fields for NameID, SCIM Username, First Name, and Last Name, with action buttons for 'Delete' and 'Save' in the bottom right corner.

Frequently asked questions  

What are the default mappings?

  • Office in OneLogin → Office in Dialpad
  • Number in OneLogin → Number in Dialpad
  • Email(s) in OneLogin → Email(s) in Dialpad
  • Username in OneLogin → Username in Dialpad
  • First name in OneLogin → First name in Dialpad
  • Last name in OneLogin → Last name in Dialpad

What happens to existing Users once SCIM is added to the company?

Any users that already exist in both Dialpad and OneLogin get linked together using their email address to determine which corresponds to which, and any fields that were out of sync will be communicated to OneLogin.

How is a number assigned?

Dialpad assigns a number from the Office's reserved pool. If there are no numbers in your Reserve Pool, we use the area code of the Office to which the User is assigned to.

Related to

Was this article helpful?
0 out of 0 found this helpful

Comments

0 comments

Article is closed for comments.