# Establishing Okta SSO Authentication in CData Sync **URL:** \ **Category:** Editions\ **Tags:** article, cdata-sync, okta, sso\ **Created:** [October 12, 2023, 9:28pm UTC](https://community.cdata.com/t/establishing-okta-sso-authentication-in-cdata-sync/457 "2023-10-12T21:28:20Z")\ **Posts on this page:** 1\ **Page:** 1
**Author:** ![Bukuroshe\_D](https://avatars.discourse-cdn.com/v4/letter/b/50afbb/32.png) [@Bukuroshe\_D](https://community.cdata.com/u/Bukuroshe_D)\ **Post date:** [October 12, 2023, 9:28pm UTC](https://community.cdata.com/t/establishing-okta-sso-authentication-in-cdata-sync/457/1 "2023-10-12T21:28:20Z")
Single Sign-On (SSO) in CData Sync using Okta SSO provider enhances the user experience with CData Sync and improves security and productivity, which helps create efficient, user-friendly and robust access to the application. With SSO, your organization can have multiple instances of CData Sync and all be accessible simultaneously from anywhere around the world. This article provides step-by-step instructions for configuring Single Sign-On (SSO) authentication in CData Sync using Okta SSO provider. **Configuring Okta SSO Authentication in CData Sync** The basic steps for setting up Single Sign-On (SSO) Authentication with Okta in CData Sync are as follows: 1. Configure Okta 2. Configure User in Sync 3. Configure SSO in Sync **Section I: Configure Okta** 1. Create a custom app integration 1. In the Okta Admin Console, navigate to **Applications** \> **Applications**. 2. Click Create App Integration. ![e453084c-fecb-4ad8-9336-2d71f4701f93.png](https://us1.discourse-cdn.com/cdata/original/1X/311b3caa96c911a4ba5458890c7d6f058c898bce.png) 1. Select **OIDC - OpenID Connect** as the **Sign-in method** and W **eb Application** as the **Application type** then click **Next**. ![ad4ee095-2473-4012-9886-437053163ccf.png](https://us1.discourse-cdn.com/cdata/original/2X/7/74076d21f67976e96ecd07e3c823072b51c263ab.png) 1. Configure the following: _Enter the_ _ **App integration name** _ _Add the_ _ **Sign-in redirect URIs** _ as applicable to your CData Sync instance: _ **Java** __:_ [http://localhost:8181/src/ssoCallback.rst](http://localhost:8181/src/ssoCallback.rst) **[ADO.NET](http://ADO.NET):** [http://localhost:8019/src/ssoCallback.rst](http://localhost:8019/src/ssoCallback.rst) ![06c26f0e-414e-4feb-a079-c7f595831fbd.png](https://us1.discourse-cdn.com/cdata/original/1X/67d7715231cf5861a2c834dc5b3c3a3f332d9f1b.png) _ **Note** __: Please specify the corresponding port as per your instance._ 1. Select the desired **Assignments** option. 2. Click **Save** to create the app. 3. Retrieve the necessary properties from Okta 1. After the application is successfully created, click on _ **General** _ and note the values of Client ID and Client Secret: ![fd127e6e-3487-4899-98de-8ac28db71d26.png](https://us1.discourse-cdn.com/cdata/original/2X/6/69fba4c0d301f842d855c5160cf6b9e49bfa5e8c.png) 1. Navigate to _ **Sign On** _ and note the value of Audience: ![9b50c434-12f5-4417-811a-5acca43270c3.png](https://us1.discourse-cdn.com/cdata/original/2X/6/6075d2a59a13ee3d1d484d60a4a196dd5ada7548.png) _ **Note** __: In this article we have used the custom authorization server called_ _default_ _that Okta provides, however you can set up your own custom authorization server._ **Section II: Configure User in Sync** This section focuses on configuring user-specific settings within the CData Sync application. 1. Open CData Sync and navigate to **Settings** \> **Users** \> **Add**. 2. Set up the **User** and its corresponding password. 3. Choose the **Role** as per your use case. 4. Specify **Federation ID** depending on the key claim value. 5. Click on **Add** and refresh the page. **Section III: Configure SSO in Sync** In this section you will configure the necessary SSO settings within the CData Sync application. This step ensures that CData Sync can initiate and manage the SSO authentication process effectively. 1. Open Sync and navigate to **Settings** \> **SSO**. 2. Click on **Configure**. 3. The Single Sign On (SSO) Settings windows appears. Fill in the following details: **Audience URIs** : Set this value to the URI that identifies Sync as a trusted application within the SSO platform _(the value you noted in_ **_section_ _I_ _\>_ _step 2.2_** _)._ **Key Claim** : This setting specifies what value from the identity provider should be treated as the federation Id. This value can usually be set to sub but it might depend on your authorization server. **OAuth Client ID** : Set this to the client Id from the app integration that you created, _(the value_ _you retrieved in_ **_section I_ _\>_ _step 2.1_** _)._ **OAuth Client Secret** : Set to the client secret in your application settings _(the value_ _you retrieved in_ **_section I_ _\>_ _step 2.1_** _)._ **Import URL** : You can get the discovery URL from [here](https://developer.okta.com/docs/guides/sign-into-mobile-app-redirect/android/main/#configure-your-app:~:text=Value-,%3CDISCOVERY_URL%3E,-The%20domain%20of) for Okta. After specifying the OpenID Discovery URL, you can click the _ **Import** _ button to automatically import the other settings such _as Authorization URL, Default Scopes __,_ _Token Issuer Identifier__ ,_ _Token URL,_ _Issuer Certificate…_ ![b8e6f09a-6098-49cd-8399-34c91cf603f6.png](https://us1.discourse-cdn.com/cdata/original/2X/f/fb19d9a258baeb107e76d33975a5a64dd438f399.png) _ **Note** :_ _In this article we have used the Import button to automatically import some SSO settings, however you can set these settings manually._ 1. Click on **Save**.    _ **Note** __: For more information, you can also refer to our_ [_Help_](https://cdn.cdata.com/help/ASH/sync/Single-Sign-On.html) _documentation._ 2. The Okta SSO authentication is now configured for CData Sync. You can also see the changes in the log in page of the application: ![a63a2376-065f-4603-af7d-f49050cb4d5a.png](https://us1.discourse-cdn.com/cdata/original/1X/8bc12e75ceee1565d6075dc8e8ed84cb01a44e16.png) Please reach out to [support@cdata.com](mailto:support@cdata.com) if you run into any issues.