What are Cached Credentials?Ĭached credentials allow a user to access machine resources when a domain controller is unavailable.Īfter a successful domain logon, a form of the logon information is cached. This is great when a user is authenticating directly against a domain controller but not so good when a user, especially a remote user, is logging onto a machine or a VPN connection using Windows cached credentials. SSPR solutions typically allow a user to easily reset her Active Directory password. An SSPR solution allows the AD credentials to be reset but does nothing to affect the cached credentials on the client machine. The important part here is that the user is not authenticating directly against a Windows domain controller for authentication. This includes VPN-connected users as well as users who take advantage of resources like portals that store user credentials in AD. Basically, this scenario-supported with solutions like Web Active Directory’s PeoplePassword product-occurs when users who don’t regularly log directly into a domain and authenticate against a domain controller forget their Windows password. Understanding cached credentials is particularly important when working with remote users in a SSPR (self-service password reset) scenario. We take a closer look at some best practices to avoid account lockout issues when cached credentials and AD credentials become out of sync.

Since we provide Active Directory solutions, it would make sense that we have insight into AD credentials caching in Windows but the caching mechanism is actually a function of the client and not the server.

We get questions about Active Directory credential caching quite often from customers and prospects.

Remove cached skype for business login