--- title: "Okta Single Sign-On via SAML" slug: "okta-single-sign-on-via-saml" description: "Sign into Dialpad using your Okta SAML" updated: 2024-12-13T22:41:21Z published: 2024-12-13T22:41:21Z --- > ## Documentation Index > Fetch the complete documentation index at: https://help.dialpad.com/llms.txt > Use this file to discover all available pages before exploring further. # 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](http://saml-doc.okta.com/SAML_Docs/How-to-Configure-SAML-2.0-for-Dialpad.html). 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 ![Screen_Shot_2022-05-09_at_8.11.30_AM.png](https://cdn.us.document360.io/0f28ad44-2863-4372-a27e-c6728808d742/Images/Documentation/screen_shot_2022-05-09_at_8.png) 5. Select **Add**, enter an **Application Label** 6. Select**D****one** ![Screen_Shot_2022-05-09_at_8.12.57_AM.png](https://cdn.us.document360.io/0f28ad44-2863-4372-a27e-c6728808d742/Images/Documentation/screen_shot_2022-05-09_at_8(1).png) That's it! You'll now see the Dialpad application instance created for your org. ## Configure Dialpad attributes in Okta Next, it's time to configure your Dialpad service provider attributes in Okta. Let's take a look at the steps required using our example domain (lojackphone.com) In 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 ![](https://cdn.us.document360.io/0f28ad44-2863-4372-a27e-c6728808d742/Images/Documentation/image-1717689594192.png) In the Okta admin tab of the browser, where the Dialpad application was previously configured, navigate to **Sign On** and click on **Edit** ![Screen_Shot_2022-05-09_at_8.18.37_AM.png](https://cdn.us.document360.io/0f28ad44-2863-4372-a27e-c6728808d742/Images/Documentation/screen_shot_2022-05-09_at_8(3).png) Navigate to **Advanced Sign-On Settings,** and paste the SP (Service Provider) related attributes in the corresponding fields: ![Screen_Shot_2022-05-09_at_8.19.28_AM.png](https://cdn.us.document360.io/0f28ad44-2863-4372-a27e-c6728808d742/Images/Documentation/screen_shot_2022-05-09_at_8(4).png) Navigate to **Credentials Details**, choose the **Application username format** as **Email,** and click on Save. ![Screen_Shot_2022-05-09_at_8.20.16_AM.png](https://cdn.us.document360.io/0f28ad44-2863-4372-a27e-c6728808d742/Images/Documentation/screen_shot_2022-05-09_at_8(5).png) ## 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 ![Screen_Shot_2022-05-09_at_8.24.49_AM.png](https://cdn.us.document360.io/0f28ad44-2863-4372-a27e-c6728808d742/Images/Documentation/screen_shot_2022-05-09_at_8(6).png)** 3. Take note of the**IDP Entity ID(Issuer), IDP SSO URL, and Certificate** 1. That the actual values would differ, reflecting your org URL in Okta ![Screen_Shot_2022-05-09_at_8.25.31_AM.png](https://cdn.us.document360.io/0f28ad44-2863-4372-a27e-c6728808d742/Images/Documentation/screen_shot_2022-05-09_at_8(7).png) 4. Navigate back to your **Okta SAMLConfiguration** page on the **Dialpad** web portal to paste in your values and save your changes. ![Screen_Shot_2022-05-09_at_8.26.11_AM.png](https://cdn.us.document360.io/0f28ad44-2863-4372-a27e-c6728808d742/Images/Documentation/screen_shot_2022-05-09_at_8(8).png) ## 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. NoteBefore 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** **![Screen_Shot_2022-05-09_at_8.30.23_AM.png](https://cdn.us.document360.io/0f28ad44-2863-4372-a27e-c6728808d742/Images/Documentation/screen_shot_2022-05-09_at_8(9).png)** 1. ****Enter the **domain of your Company** ******![Screen_Shot_2022-05-09_at_8.32.11_AM.png](https://cdn.us.document360.io/0f28ad44-2863-4372-a27e-c6728808d742/Images/Documentation/screen_shot_2022-05-09_at_8(10).png)** 2. ****Enter your Okta credentials 3. ****Select****Sign In**** **![okta_login.png](https://cdn.us.document360.io/0f28ad44-2863-4372-a27e-c6728808d742/Images/Documentation/okta_login.png)** ## 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 ![](https://cdn.us.document360.io/0f28ad44-2863-4372-a27e-c6728808d742/Images/Documentation/image-1717143672872.png) 2. Navigate to **Authentication** 3. Select **SAML** 4. Select **Prevent users from logging in with other SSO providers** 5. Select **Save** ![](https://cdn.us.document360.io/0f28ad44-2863-4372-a27e-c6728808d742/Images/Documentation/image-1717689036850.png) NoteOnce saved, your users won't be able to use Microsoft and Google SSO (or even their username and password) to log in to Dialpad. ## Related - [Manage Users with Okta SCIM](/manage-users-with-okta-scim.md) - [Syncing Dialpad Phone Numbers to Okta](/syncing-dialpad-phone-numbers-to-okta.md)