Articles in this section

Okta Single Sign-On via SAML

Rather than signing into Dialpad with your Google or Microsoft productivity suite, our Okta integration allows your team to access Dialpad via Okta's single sign-on option (SSO) via SAML.

Let's dive into the details.

Who can use this

Dialpad's Okta integrations are available to all Dialpad users.

In order to enable Okta SSO via SAML, you will need to have Company Admin access to your company's Dialpad Account.

Add the application

First things first, you'll need to add the application. 

  1. Log into Okta
  2. Navigate to Applications
  3. Select Browse App Catalog 
  4. Search for “Dialpad” and select the Dialpad (SAML, Provisioning) integration
    Screenshot of the Okta Browse App Integration Catalog page displaying Dialpad typed into the search bar, with the Dialpad (SAML, Provisioning) integration highlighted in the search results.
  5. Select Add, enter an Application Label 
  6. Select Done
    Screenshot of the Okta Add Dialpad application setup screen showing 'Dialpad' entered in the Application label field under General settings, with a blue 'Add' button on the top left overview panel and a blue 'Done' button at the bottom right.

That's it! You'll now see the Dialpad application instance created for your org.

Configure Dialpad attributes in Okta

Next, configure your Dialpad service provider attributes in Okta. 

Let's take a look at the steps required using our example domain (lojackphone.com)

In a new tab, navigate to your Dialpad Admin Settings.

  1. Select Company Settings
  2. Select Authentication 
  3. Select SAML 
  4. Select Okta from the provider drop-down
    Screenshot of the Dialpad SAML Configuration page with orange boxes highlighting the selected SAML option under Authentication and the provider drop-down menu set to Okta.

In the Okta admin tab of the browser, where the Dialpad application was previously configured, navigate to Sign On and click on Edit

Screenshot of the Dialpad application settings in Okta showing the selected Sign On tab and an Edit link in the top-right corner of the Settings panel.

Navigate to Advanced Sign-On Settings, and paste the SP (Service Provider) related attributes in the corresponding fields:

Screenshot of the Advanced Sign-on Settings configuration in Okta, displaying populated text fields for SP SSO Url (ACS) and SP Entity ID using example URLs for lojackphone.com.

Navigate to Credentials Details, choose the Application username format as Email, and click on Save.

Screenshot of the Credentials Details section in Okta displaying Application username format set to Email and a blue Save button in the bottom-right corner.

Configure Okta identity provider attributes into Dialpad

Now it's time to configure the Okta identity provider attributes into Dialpad. 

From the Okta admin tab of the browser, where the Dialpad application was previously configured:

  1. Navigate to the Sign On tab 
  2. Select View Setup Instructions 
    Screenshot of an Okta notification box stating SAML 2.0 setup requirements with a blue View Setup Instructions button.
  3. Take note of the IDP Entity ID(Issuer), IDP SSO URL, and Certificate
    • That the actual values would differ, reflecting your org URL in Okta
      Screenshot of Okta setup instructions showing fields for IdP SSO URL, IdP Entity ID (Issuer), and the X.509 Certificate text box.
  4. Navigate back to your Okta SAMLConfiguration page on the Dialpad web portal to paste in your values and save your changes.
Screenshot of the Dialpad SAML Configuration page displaying populated fields for IdP SSO Url, IdP Entity ID (Issuer), and the Certificate text area above a purple Save button.

Login with Okta

To make life nice and easy, Users can log in with Okta right from their Dialpad app (desktop + mobile), or web portal. 

Note

Before a User can use Okta SSO, they must already exist within Okta, and be provisioned in Dialpad.

To log into Dialpad with Okta, simply select Login with another provider
Screenshot of the Dialpad login page at dialpad.com/login displaying options to 'Log in with Google', 'Log in with Microsoft', and a link at the bottom to 'Log in with another provider'.

 

  1. Enter the domain of your Company
    Screenshot of the Dialpad Login With Another Provider screen showing lojackphone.com entered in the domain input field above Cancel and Next buttons.
  2. Enter your Okta credentials
  3. Select Sign In

                   Screenshot of the Okta Sign In prompt showing fields for Username and Password, a Remember me checkbox, and a blue Sign In button.

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 Company from the drop-down at the top left
    Screenshot of the Dialpad Admin Settings page with an orange arrow pointing to My company highlighted in the top-left dropdown menu, alongside an orange circle around the gear icon on the left navigation panel.
  2. Navigate to Authentication
  3. Select SAML
  4. Select Prevent users from logging in with other SSO providers
  5. Select Save 
    Screenshot of the Dialpad SAML Configuration (okta) page with orange boxes highlighting the selected SAML option under Authentication, the gear settings icon on the left navigation panel, and the Prevent users from logging in with other SSO providers option above the purple Save button.

Note

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.

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

Comments

0 comments

Article is closed for comments.