Tips for finding Knowledge Articles

  • - Enter just a few key words related to your question or problem
  • - Add Key words to refine your search as necessary
  • - Do not use punctuation
  • - Search is not case sensitive
  • - Avoid non-descriptive filler words like "how", "the", "what", etc.
  • - If you do not find what you are looking for the first time,reduce the number of key words you enter and try searching again.
  • - Minimum supported Internet Explorer version is IE9
Home  >
article

KB-4214: ZPA cannot find user's primary group for provisioning

Centrify DirectControl ,   Centrify Identity Service, Mac Edition ,  

12 April,16 at 11:46 AM

Applies to: All versions of Centrify DirectControl for UNIX/Liunx
 
Question:
 
Zone Provisioning Agent (ZPA) is monitoring a zone for user auto-provisioning. The source group is from machine domain and a user from cross-forest user domain is a member of this source group. (Machine domain and user domain are in 2-way trust relationship.)
 
In Provisioning tab of zone's properties page, primary group is configured to be based on "Active Directory group membership". Primary groups of users from user domain are located in machine domain, and users are the member of their corresponding primary groups. ZPA service account has the read permission to read the primary group of users from both machine and user domains.
 
However, when trying to provision user from user domain into zone, the following error is shown in the ZPA log: 
 
[2014-02-26 07:47:11.761 +0000] zoneupdate.exe[5708,1] Information: ZoneWorker.OutputMessage: <userA>@<user.domain>
[2014-02-26 07:47:11.979 +0000] zoneupdate.exe[5708,1] Information: ZoneWorker.OutputMessage: ... [Finding Primary Group] 
[2014-02-26 07:47:12.776 +0000] zoneupdate.exe[5708,1] Information: ZoneWorker.OutputMessage: Domain Users@<user.domain> ... [NOT IN ZONE] 
[2014-02-26 07:47:12.792 +0000] zoneupdate.exe[5708,1] Information: ZoneWorker.OutputMessage: ... [ERROR: No primary group found.] 
 
Primary group of the user (as mentioned, located in machine domain) has already been added into zone, i.e zone-enabled. What is the reason ZPA is unable to find the user's primary group and fails?
 
Answer:
 
From the ZPA log above, ZPA is only trying to find the group membership in the user domain. To instruct ZPA to search also the group membership in the machine domain, it is suggested to add the following in Registry:
 
Reg key: HKEY_LOCAL_MACHINE\Software\Centrify ZPA
 
Reg value under this key: GroupLookupDomains (Note: the type should be Multi-String Value)
 
Then specify domain names (i.e. both user domain and machine domain in this scenario) in this value line by line, for example: 
 
User-added image
 
Caution: Please make sure there are no trailing spaces after the domain names. Otherwise, the following exception will throw in ZPA log and provisioning will fail:
 
[2014-02-28 09:22:19.906 +0000] zoneupdate.exe[6712,1] Information: ZoneWorker.OutputMessage: ... [Finding Primary Group] 
[2014-02-28 09:22:20.093 +0000] zoneupdate.exe[6712,1] Verbose: PrincipalData.GetGroups: Lookup groups in domain: <machine.domain> 
[2014-02-28 09:22:20.109 +0000] zoneupdate.exe[6712,1] Verbose: PrincipalData.GetGroups: Cannot lookup groups in domain <machine.domain>
[2014-02-28 09:22:20.109 +0000] zoneupdate.exe[6712,1] Verbose: PrincipalData.GetGroups: System.DirectoryServices.ActiveDirectory.ActiveDirectoryObjectNotFoundException: The specified domain does not exist or cannot be contacted. 
[2014-02-28 09:22:20.109 +0000] zoneupdate.exe[6712,1] Verbose: PrincipalData.GetGroups: at System.DirectoryServices.ActiveDirectory.Domain.GetDomain(DirectoryContext context) 
[2014-02-28 09:22:20.109 +0000] zoneupdate.exe[6712,1] Verbose: PrincipalData.GetGroups: at Centrify.Provisioning.PrincipalContexts.get_Item(String domain) 
[2014-02-28 09:22:20.109 +0000] zoneupdate.exe[6712,1] Verbose: PrincipalData.GetGroups: at Centrify.Provisioning.ZoneWorker.PrincipalData.GetGroups(String[] domains) 
 
After the changes in Registry, ZPA should now be able to provision users from machine domain into zone, and from the ZPA log:
 
[2014-02-28 16:08:29.991 +0800] Centrify.Provisioning.Agent.exe[12124,6] Verbose: PrincipalData.GetGroups: Lookup groups in domain: <user.domain>
[2014-02-28 16:08:30.116 +0800] Centrify.Provisioning.Agent.exe[12124,6] Verbose: PrincipalData.GetGroups: Lookup groups in domain: <machine.domain>
 
it shows that ZPA is getting the registry setting and then later trying to find the group membership from both domains:
 
[2014-02-28 09:22:19.906 +0000] zoneupdate.exe[6712,1] Information: ZoneWorker.OutputMessage: ... [Finding Primary Group] 
[2014-02-28 09:22:20.093 +0000] zoneupdate.exe[6712,1] Verbose: PrincipalData.GetGroups: Lookup groups in domain: <user.domain> 
...
[2014-02-28 09:22:20.109 +0000] zoneupdate.exe[6712,1] Verbose: PrincipalData.GetGroups: Lookup groups in domain: <machine.domain>

Still have questions? Click here to log a technical support case, or collaborate with your peers in Centrify's Online Community.