Why kerberos keytab will not stay in sync with Active Directory kvno version

Solution Verified - Updated -

Issue

The local /etc/krb5.keytab will become outdated every 7 to 14 days. The Active Directory KDC controller will report a newer kvno number. This version number will be larger than the local system keytab kvno version. When the kvno version mismatches, the local principal is no longer valid and all attempts to use this for authentication will fail.

Environment

  • Red Hat Enterprise Linux 5
  • Red Hat Enterprise Linux 6
  • kerberos
  • samba

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content