Solved

LDAP authentication and cached passwords

Posted on 2007-11-28
4
491 Views
Last Modified: 2013-12-04
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?  
0
Comment
Question by:Lombwar
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 2
  • 2
4 Comments
 
LVL 30

Expert Comment

by:LauraEHunterMVP
ID: 20367984
Documented change in 2K3 SP1.  Auth via LDAP with DN must not considered “Interactive logon” and therefore follows the rule that was implemented in Server 2003 SP1 that allows for the old password to be used for 1 hour after password change.

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
0
 

Author Comment

by:Lombwar
ID: 20368218
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
0
 
LVL 30

Accepted Solution

by:
LauraEHunterMVP earned 125 total points
ID: 20368247
Correct.  Behaviour exists in SP1 or later.
0
 

Author Closing Comment

by:Lombwar
ID: 31411495
Thanks for the quick response
0

Featured Post

Why You Need a DevOps Toolchain

IT needs to deliver services with more agility and velocity. IT must roll out application features and innovations faster to keep up with customer demands, which is where a DevOps toolchain steps in. View the infographic to see why you need a DevOps toolchain.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Suggested Solutions

Title # Comments Views Activity
Installing 2012 R2 and making it a domain controller 6 53
DNS logs 1 33
Server 2003 Active Directory tombstoned 24 23
Active Directory GPOs and OUs 2 19
This article shows how to deploy dynamic backgrounds to computers depending on the aspect ratio of display
A company’s centralized system that manages user data, security, and distributed resources is often a focus of criminal attention. Active Directory (AD) is no exception. In truth, it’s even more likely to be targeted due to the number of companies …
This Micro Tutorial hows how you can integrate  Mac OSX to a Windows Active Directory Domain. Apple has made it easy to allow users to bind their macs to a windows domain with relative ease. The following video show how to bind OSX Mavericks to …
This video shows how to use Hyena, from SystemTools Software, to bulk import 100 user accounts from an external text file. View in 1080p for best video quality.

752 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question