Centrify

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-3089: Zone Provisioning Agent (ZPA) will replace invalid UNIX characters for login name with a underscore

Centrify DirectControl ,  

12 April,16 at 11:09 AM

Applies to: All versions of Centrify DirectControl using Zone Provisioning Agent.
 
Problem:
 
If the samAccountName / login name has an invalid character in it, Zone Provisioning Agent (ZPA) will replace the invalid character with an underscore (_). 
 
For example if the login name is joe.smith, ZPA will replace this with joe_smith. This will cause an authentication conflict if a user home directory is configured for a network home directory. A network home directory will typically display the samAccountName.

 
Cause:
 
This behavior in ZPA is by design and is configurable. 

 
Resolution:
 
Under the ZPA Provisioning tab, there is a settings gear icon next to the Login name field. Add the 'character' in the 'Valid characters for UNIX names field:
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 














 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 












 
After saving the Unix character, either:
 
  • I. Remove and then add the users back into the AD group (This is the source group set in the ZPA provisioning tab).
     
  • II. Or disable ZPA in Zone Provisioning and delete the user profiles from the Zone. Then re-enable ZPA provisioning to regenerate the update zone profiles. This will reflect the new changes in the login name. 
Note: Make sure the ZPA service is restarted to take effect. 

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

Related Articles

 articleKB-7555: Unable to login as root after upgrade to Centrify Suite 2016 (CDC 5.3.0) articleKB-6771: Configuring ZPA to Remove Unwanted Characters from Unix Login Names articleKB-6073: How to join the Linux/Unix Centrify Server to Active Directory with specific Computer Role? articleKB-3925: How to add Centrify parameter to a group policy articleKB-6041: How to show current license type in use by adclient? articleKB-6056: How to report the group policy settings that are in effect for the local computer? articleKB-6040: How to change the license type in use after adclient successful joined to the AD? articleKB-6038: How to specify the license type to use when joining the server to AD using adjoin? articleKB-3317: Troubleshooting steps for when the ZPA isn't working properly articleKB-6050: How to configure a group for automatic Kerberos Credentials for infinite renewal?