A user logs into Vault through a configured LDAP auth method and notices that re-authentication...

Vault authentication produces a client token, and non-root tokens normally have a time-to-live. If the token is not renewed before its TTL expires, Vault revokes the token and its associated leases, forcing the user to authenticate again. In this scenario, the repeated eight-hour login cycle indicates that the LDAP-authenticated token has an eight-hour effective TTL or auth lease. The issue is not caused by entering the wrong token repeatedly, because that is not how Vault normally handles LDAP login expiration. Revoking the root token would not directly force all LDAP users to reauthenticate every eight hours. A changed LDAP password could cause failed authentication, but it would not explain a predictable reauthentication interval. HashiCorp documents that auth identities have leases and non-root tokens stop functioning after their TTL expires.

================