--- title: "Connecting with multiple Identity Providers" canonical: "https://helpcenter.mindproapps.com/space/SDC/2347729318/Connecting%20with%20multiple%20Identity%20Providers" format: markdown --- > ℹ️ **Summary: **Learn how to setup and manage the connections with multiple identity providers simultaneously. ### **Connecting with multiple identity providers** Mindpro Sync allows you to connect with multiple providers simultaneously. This way, even if your company has different directories, you can integrate your instance to obtain data from these different sources of information. See some examples of use cases of companies that use multiple identity providers: - Quickly consolidate user management of an acquired company's IDP within the parent company. - Maintain identity providers for separated departments' domains within a company. - Meet certain data residency requirements where each region needs its own identity provider. Whatever the case, if you use multiple identity providers in your company, you can use Mindpro Sync to connect to these directories simultaneously. ![Mindpro-1722545355938-1x.png](media://a7531c7f-be9f-4793-bc63-70f4ef8b4814) --- ### **Creating multiple connections with identity providers** To establish a connection with one or more identity providers, repeat the same steps to create a connection: - 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. - From the available options, **select your Identity Provider **to connect and fill in the fields accordingly. - After informing all data and clicking on **Connect**, the system validates the connection with the IDP and informs in case any issue occurs. - The system will show a “**Success**” message confirming the connection and enable the Synchronization tab as soon as the connection is established. - After this, the system will enable the **Synchronization tab**, where the user can select the attribute (containing a valid email) to sync the user’s data with Jira and also the manager attribute to be used for assigning approvals and displaying the user hierarchy inside issues. - With the synchronization field selected, click **Save**. --- ### **Changing the priority of your connections with the Identity Providers**   When you have multiple connections, you can define the priority order for them 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.  Let's use the list below as an example. There are 4 connections, and they were ordered according to the priority defined by the admin. **Context** - "Company ABC" acquires "Company XYZ" and integrates their user directories, Okta (1) and OneLogin (3), respectively. - The user "John Snow" is present in both identity providers, with the same email address. He is not present in any other connection. - "John Snow" is the reporter for the related Jira Issues. - Mindpro Sync is configured to show the reporter's data in the issues. ![Mindpro-1722545463995-1x.png](media://97685553-3f89-41b6-968d-0eccca4b9b3c) **Scenario 1** - When an issue is created (with "John Snow" as a reporter), the system will first check the connection with the highest priority order. - If the user is found there, then the system will pick up John's attributes from Okta to display in the issue. **Scenario 2** - If the user is not found in the first connection (Okta), the system will look for the next priority order. - The second connection is disconnected (Azure AD), so the system will skip that one and move to the next active connection. - The system founds the user in the third connection. When an issue is created, the system will use John's attributes from OneLogin display in the issue. **Scenario 3** - The user is not found in any of the existing connections. - When the issue is created, the system will inform, via the "Hierarchy" panel that no data could be retrieved since the user was not found in the directory. **Context ** Now, let's change the priority order for the existing connections, but use the same context. The new priority order is: ![Mindpro-1722545722405-1x.png](media://56bd2f7a-60a2-4c62-b774-ae014f5a886d) **Scenario 4** - The system will look for "John Snow" in the first connection but will not find him, since he is not present there. - The system finds the user in the second connection, which is now the one connected with OneLogin. - When an issue is created, the system will use John's attributes from OneLogin display in the issue. > ℹ️ **Good to know** > ℹ️ > ℹ️ Mindpro Sync currently support connections with the following sources of data: > ℹ️ > ℹ️ - [Active Directory](https://mindpro.atlassian.net/wiki/spaces/SDC/pages/2348318724) > ℹ️ - [Azure AD](https://helpcenter.mindproapps.com/space/sync/1987477513) > ℹ️ - [Okta](https://helpcenter.mindproapps.com/space/sync/1987379205) > ℹ️ - [Onelogin](https://helpcenter.mindproapps.com/space/sync/1988362254) > ℹ️ - [Microsoft 365](https://helpcenter.mindproapps.com/space/sync/1988034626) > ℹ️ > ℹ️ Use the links above to learn more how to setup the connection with these sources. --- ### **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)