Shared Services NOT Recognizing Users and Groups in Differing AD Domains
SummaryShared Services NOT Recognizing Users and Groups in Differing AD Domains
I am having a problem with Shared Services recognizing Users/Groups across Microsoft Active Directory (MSAD) domains. Here's an example of the issue:
- Group1 is in MSAD Domain1
- User1 is a member of Group1, User1 is a member of MSAD Domain1
- User2 is a member of Group1, User2 is a member of MSAD Domain2 (a different domain than Group1)
- Group1 is provisioned using Shared Services
We have added a "Global" MSAD domain to Shared Services which pulls data for all domains at our company. We are able to see both User1 and User2 as members of Group1 in Shared Services despite User2 being in a different domain than Group1. User1 is getting the appropriate level of access and can access Essbase as expected. User2 is not getting any Essbase access despite being in Group1 and showing up in Shared Services as a member of Group1.