topic Re: User-ID Group Mapping for Multi Domain Single forest in General Topics

User-ID Group Mapping for Multi Domain Single forest

jezkerwin — Tue, 22 Mar 2016 05:27:24 GMT

Hi everyone.

I'm trying to setup a User-ID installation for our multi-domain Active Directory environment.

Here is a rundown on what we have

DomainA = Workstations, groups, users, servers, etc. The main domain where everything is conducted

DomainB = legacy domain where some user accounts are located.

I've installed the User-ID agent on a Windows VM running in DomainA and have configured the PA F/W to talk to DomainA for LDAP and User-ID.

The Groups that I want to use as part of the Policy are located in DomainA. Those groups have members from DomainB.

In the monitor tab I can see users from DomainB being matched correctly and if I set the policy to a user directly it will match. However where I'm having issues is that if I specifiy a group in DomainA as part of the policy, it's not matching for the user in DomainB.

So my question is (after that long winded explanation), can my wanted setup work or do I have to do thing differently?

Thanks.

Re: User-ID Group Mapping for Multi Domain Single forest

reaper — Tue, 22 Mar 2016 09:27:35 GMT

If I understand your explanation correctly, you are seeing users from domain B in their proper form (domainb\user) in the user-ip mapping. if you add a second LDAP server profile to match domain B groups, you should be able to also have domain B groups in the policy

Re: User-ID Group Mapping for Multi Domain Single forest

jezkerwin — Tue, 22 Mar 2016 10:45:33 GMT

correct, in the monitor tab I can correctly see domainB\user being resolved.

in the policy though, if I configure domainA\group as the user and domainB\user is a member of that group, it wasn't resolving the lookup to the group and the policy would fail.

I'm not sure which group type to user Global, Domain Local, Universal. I have the LDAP server profile talking to the Global Catalog.

I'll try with the second LDAP profile talking to domainB and see if that works.