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-0168: groups are not interpreted on 'id -a' command

Centrify DirectControl ,  

12 April,16 at 11:24 AM

Problem:

When logged in as AD User and executing:

id -a
OR
id -a ADuser

as root user, the ADUser's secondary groups are not interpreted, just the gids are displayed.

Example: uid=100(Ian) gid=1000(admin), groups=2000,301,1002

The centrifydc.log tells in that case that there are a lot of disconnects while ldap searches against the Windows DC.


Resolution:

This issue can be solved by editing the /etc/centrify/centrifydc.conf file. Open the /etc/centrify/centrifydc.conf in an editor and look for

adclient.fetch.object.count=100

and set it to a lower value eg. 5 and re-start centrifydc.

Execute the above command again. Now values should be displayed correctly.

The example above should show up like:
uid=100(Ian) gid=1000(admin), groups=2000(sup),301(prod),1002(doc)

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