Hmm... that's an old version. Perhaps this is not a new issue.
Can you confirm that this is happening only on that system? and that it was working before? (or perhaps this has been an old issue); if it was working, what happened between it worked vs. now?
My advice (because this seems to be a local issue, based on your description) is that you do an SSH trace and find the root of the problem. In addition, the whole idea about using a solution like Centrify for UNIX/Linux is to consolidate the identity sources. If you have users signing-in with their AD credential (username/password or Kerberos SSO) AND with SSH keys, this is a redundancy that causes these types of errors.
To do an SSH trace, do the following:
- In the server exhibiting the issue, run sudo /usr/share/centrifydc/sbin/sshd -ddde -p 2222 to start the SSHD server in the foreground with verbosity turned on.
- From the ssh client, connect to the SSHD server on port 2222,
ssh -p 2222 -vvv <hostname> - Pay close attention to the session on the server
Most of the time, the issue may be related to the user not typing the password correctly, or simply a configuration issue.
Please note, since you're using Express, the current community supported version is 5.4.x and Centrify-enhanced OpenSSH is an optional component.