Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

It looks as though there is a solid requirement for usernames on the UNIX client and in the MSAD to match for kerberos authentication to function (I think LDAP authentication too). Is this absolutely the case?

Our infrastructure owners have a habit of changing the samaccountName without warning - implementing UNIX/MASD Kerberos/LDAP authentication like this becomes a bit of a nightmare in this situation.

Could we alter the user mapping module to reference a different AD attribute (that doesn't change) perhaps?

share|improve this question

Unix users can list their (possibly mutiple) Kerberos principals in $HOME/.k5login.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.