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-3705: Cannot login AD user via SSH (not listed in AllowGroups)

Centrify DirectControl ,  

3 March,17 at 09:01 PM

Applies To:

All versions of Centrify DirectControl


Problem:

Users are denied access when trying to login via SSH. The following message is seen in the ssh debug logs:
 
User <user_name> not allowed because none of user's groups are listed in AllowGroups


Cause:

OpenSSH’s configuration file is sshd_config. If using Centrify-Enabled OpenSSH, the path is /etc/centrifydc/ssh/sshd_config.

By default, the AllowGroups parameter does not exist in sshd_config, but is a valid parameter.

If added in sshd_config with a space-delimited list of groups, SSH login access is restricted to users who are members of the group(s).
 
AllowGroups <unix_group_1> <unix_group_2> … <unix_group_n>

Not having AllowGroups parameter in the sshd_config file will allow all users to log in.


Resolution:
 
Either remove or remark the AllowGroups parameter in the sshd_config file or add the necessary groups that the AD users are a member to the AllowGroups parameter of to allow them to login.

After making the changes and saving the sshd_config file, restart the sshd agent for those settings to take affect.

/etc/init.d/centrify-sshd restart


Note:
See “man sshd_config” for all known parameters.

See also the following KBs:
KB-5452: How to enable debug for PuTTy / SSH clients?
KB-1698: Troubleshooting Single Sign On (SSO) issues
KB-4303: How to troubleshoot SSH Single-Sign-On (SSO) and nested SSO?
 

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-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-6073: How to join the Linux/Unix Centrify Server to Active Directory with specific Computer Role? 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-3008: AD accounts that previously worked with the built-in Apple AD plugin don't work when bound via Centrify articleKB-1330: Unable to login via ssh when a user account exists on the local machine and in Active Directory articleKB-5765: How to block OS X updates via Group Policy