Lombwar
asked on
LDAP authentication and cached passwords
Have a couple of applications that use the global catalog port 3289 to validate user logins and found that if user has changed their password, that their old password will still allow them to login for 2 - 10 hours after. They cannot use the old password to login to Windows or Exchange. Is this cached somewhere in the LDAP environment as a "grace" login, is it a replication setting till all DC have received the new object info?
ASKER
Even if we are at Service pack 2 of 2003 I am guessing that this is still set for a default of 60 minutes unless you add the entry to change the default?
This would make sense as one of the other servers that is still at 2000 when users authenticate to that this condition did not exist, so it appears to be what version of OS your authentication server is running, we also did not see this in other regions still running Win2k
This would make sense as one of the other servers that is still at 2000 when users authenticate to that this condition did not exist, so it appears to be what version of OS your authentication server is running, we also did not see this in other regions still running Win2k
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Thanks for the quick response
Samaccount name authorization via LDAP must be considered interactive logon, and therefore requires only the new password to work.
The KB reference that might explain it is http://support.microsoft.com/kb/906305