---
title: "OKTA - Connection"
canonical: "https://helpcenter.mindproapps.com/space/sync/1987870762/OKTA%20-%20Connection"
format: markdown
---
> ℹ️ **Summary: **Learn establish the Okta connection and synchronization with Mindpro Sync.

### **Okta authentication**


To establish a connection with Okta, click on the **New Connection** button on the Connections screen. 

The system will open a pop-up window with a list of options so you can select the Identity Provider you want to connect to.

![Mindpro-1774980713543-2x.png](media://11774669-9d53-4014-9a17-a3db75cf456b)


From the options available, select **Okta** as the Identity Provider to connect and fill the fields accordingly:


- **Connection Name:** Inform a name for your connection.
- **Authentication Method:** inform the way you want to authenticate your connection. The credentials will be requested according to the authentication method selected:
  - **API Token (default)**:
    - **Client URL:** Inform your Okta domain URL. This was set when you created your Okta account.
    - **Client Token: **Inform your Okta Client API Token (remember it expires every 30 days). Click [here](https://developer.okta.com/docs/guides/create-an-api-token/main/) to learn how to create one.
  - **OAuth 2.0:**
    - **Client URL:** Inform your Okta domain URL. This was set when you created your Okta account.
    - **Application Client ID: **Inform your Okta Application Client ID
    - **Application Client Secret:** Inform the client secret created for the related application in Okta
    - Click on “**Validate**” to check your connection. Okta will open a blank pop-up screen for a few seconds before validating.
    - When done, The system displays a green check icon next to the button.

![Mindpro-1774980921617-2x.png](media://b31aba15-9a82-4697-b998-8c5338f6df94)


> ⚠️ Connecting via OAuth 2.0 requires an application previously configured in Okta, with proper Client ID and Client Secret. Click [here](https://mindpro.atlassian.net/wiki/spaces/sync/pages/2154463236) to know how to configure this.


After informing all data and clicking on **Connect** the system validates the connection with Okta and informs in case any issue occurs.

As soon as the connection is established, the system will show a “Success” message confirming the connection and will enable the **Synchronization tab**.


---

### **Okta data synchronization**


When connected with Okta the system will enable the **synchronization tab** where the user can select the attribute fields to sync the user’s data with Jira and to inform the attribute that will contain the user’s manager information.

As a pre-configured option, **the system connects to the Email attributes by default**, so no action is required.

But if you want to use different IdP user attributes to sync data, select one from the list and click** Save**.

![Mindpro-1774981126070-2x.png](media://0f5d82e2-4283-46ae-b525-e87a33399fc4)


> ℹ️ **Keep in mind**
> ℹ️ 
> ℹ️ - The attribute selected for synchronization should contain a **valid email address** as a value informed in the IdP. Once selected, all users will start having their data synchronized by this attribute.
> ℹ️ - Users with a “DEPROVISIONED” status in Okta will not be synchronized, as they are set as a permanently deactivated account by the Okta Admin.

After establishing your authentication and selecting the field for data synchronization with Okta, a new connection will appear in the list of connections. In this list of connections, you will be able to view the following information and options:


- **Priority **- With multiple connections, you can define their priority order using drag and drop. The priority order defines what connection will be the reference for bringing and displaying attributes if a user is found in two or more Identity Providers.
- **Status -** Displays the current status of this connection (connected or disconnected).
- **Identity Provider **- This shows the Identity Provider used in this connection.
- **User match - **Shows the selected attribute field to be used as the key to establish the data synchronization between the Identity Provider and Jira.
- **Manager match - **This is the attribute that contains the manager's email/ID.
- **Actions -** Connection actions menu with options to edit the details, delete or disconnect the connection.


![Mindpro-1774981176155-2x.png](media://5a24b2c0-0585-4435-b720-1ac4b7078f42)


> ℹ️ **Keep in mind**
> ℹ️ 
> ℹ️ Okta works with Admin profiles to restrict users' actions. When a token is generated in Okta, it carries the admin's respective permissions. 
> ℹ️ 
> ℹ️ Depending on what is yours, you may have some limitations in terms of what attributes you can see or map from Okta. 
> ℹ️ 
> ℹ️ If that is the case, the system will display a message during the authentication process to inform you about possible restrictions. We recommend the admin have at least **“Org Admin”** permissions.

---

### **Need any help?**

Didn’t find what you were looking for? Raise a ticket [here](https://mindpro.atlassian.net/servicedesk/customer/portal/3) or get in touch at [support@mindproapps.com](mailto:support@mindproapps.com)