# Authentication with Multiple Active Directories in Identity Profile

**URL:** <https://developer.sailpoint.com/discuss/t/authentication-with-multiple-active-directories-in-identity-profile/19928>\
**Category:** SHF Discussion and Questions\
**Tags:** identity-security-cloud\
**Created:** [October 30, 2023, 6:49am UTC](https://developer.sailpoint.com/discuss/t/authentication-with-multiple-active-directories-in-identity-profile/19928 "2023-10-30T06:49:56Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![sjoyee](https://avatars.discourse-cdn.com/v4/letter/s/3ec8ea/32.png) [@sjoyee](https://developer.sailpoint.com/discuss/u/sjoyee)\
**Post date:** [October 30, 2023, 6:49am UTC](https://developer.sailpoint.com/discuss/t/authentication-with-multiple-active-directories-in-identity-profile/19928/1 "2023-10-30T06:49:56Z")

</div>

Hi all, we want to allow user to reset password and the changes will be synced to the Active Directory. I understand that the configuration is to be done in the identity profile, however only one active directory can be selected.

However, in our use cases, we have multiple active directories sources as the target systems. There isn’t any active directory as of now which consists all of the users from the authoritative source. Any input on the best approach to handle this? Since I believe the user must have the active directory selected in the identity profile to make the password reset mechanism to work.

Thank you.

---

<div class="post-metadata">

**Author:** ![sharvari](https://avatars.discourse-cdn.com/v4/letter/s/3be4f8/32.png) [@sharvari](https://developer.sailpoint.com/discuss/u/sharvari)\
**Post date:** [October 30, 2023, 7:06am UTC](https://developer.sailpoint.com/discuss/t/authentication-with-multiple-active-directories-in-identity-profile/19928/2 "2023-10-30T07:06:38Z")

</div>

If you have multiple active directories to hold certain types of users, you can try to split your Identity Profiles also accordingly and then each profile can be linked to its own AD source.

---

<div class="post-metadata">

**Author:** ![sjoyee](https://avatars.discourse-cdn.com/v4/letter/s/3ec8ea/32.png) [@sjoyee](https://developer.sailpoint.com/discuss/u/sjoyee)\
**Post date:** [October 30, 2023, 7:46am UTC](https://developer.sailpoint.com/discuss/t/authentication-with-multiple-active-directories-in-identity-profile/19928/3 "2023-10-30T07:46:31Z")

</div>

Hi Sharvari, thank you for the input. Two follow up questions if we are splitting identity profiles,

1. Do we also to split our authoritative sources into different sources to make this work?
2. In our use case, one user can also have accounts in two different AD sources, so meaning this user have to exist in two different identity profiles? So total of two identities for one same user in IDN?

Thank you.

---

<div class="post-metadata">

**Author:** ![sharvari](https://avatars.discourse-cdn.com/v4/letter/s/3be4f8/32.png) [@sharvari](https://developer.sailpoint.com/discuss/u/sharvari)\
**Post date:** [October 30, 2023, 9:31am UTC](https://developer.sailpoint.com/discuss/t/authentication-with-multiple-active-directories-in-identity-profile/19928/4 "2023-10-30T09:31:29Z")

</div>

1. Yes. You will have to split/filter the auth source as well, if you go this route.

2. There won’t be two identities per user but only one. The Profile it is part of(based on identity profile priority) and the AD source which is used on the profile would be used for reset password. The other AD account will be like a regular target AD account. If you need you could also setup password sync groups for AD sources.

---

<div class="post-metadata">

**Author:** ![system](https://global.discourse-cdn.com/sailpoint/original/2X/f/f2136700ed5e3703e0b85e02f6be799dacca7735.png) [@system](https://developer.sailpoint.com/discuss/u/system)\
**Post date:** [December 29, 2023, 9:32am UTC](https://developer.sailpoint.com/discuss/t/authentication-with-multiple-active-directories-in-identity-profile/19928/5 "2023-12-29T09:32:20Z")

</div>

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.
