Did you write the custom filter? If so, have it dump what it is doing to debug and watch it. I would be a little shocked if trust passwords were being sent through the PasswordFilter function.
 
Heh, me guessing wasn't good enough, I just tested it on K3 OEM with one of my own custom filters. Trusts do not hit the PasswordFilter function nor the PasswordChangeNotify function. Interestingly enough, computer password changes hit PasswordChangeNotify which isn't the way it used to be (I don't recall it that way anyway), however they don't hit PasswordFilter which makes sense.
 
So... You need to verify you aren't seeing something different with your filter. Once you do that you can move on to what else it might be.
 
  joe


From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Santhosh Sivarajan
Sent: Thursday, January 06, 2005 11:14 PM
To: [email protected]
Subject: [ActiveDir] Password Filter DLL and Trust Password   

I am facing an issue after installing a custom password filter DLL. Password filter DLL is working fine for user password change.  But when I try to create a trust between NT and Windows 2003, it is not accepting any password combinations.  I disable the custom password filter DLL, and then it is started accepting the trust passwords.  We don’t have any code in the password filter DLL to check the trust password.  Is it a normal behavior?  I know trust is also calling LSA to check the password complexity.  Do I need to include trust password checking code in the password filter DLL?  Is there anything else I am missing in the Password Filter DLL? How about computer passwords?

 

Any input would be greatly appreciated!

Reply via email to