PrincipalContext.ValidateCredentials exceptions when reusing object for multiple validations - by RussellChadwick

Status : 

  Not Reproducible<br /><br />
		The product team could not reproduce this item with the description and steps provided.<br /><br />
		A more detailed explanation for the resolution of this particular item may have been provided in the comments section.

Sign in
to vote
ID 768582 Comments
Status Resolved Workarounds
Type Bug Repros 3
Opened 10/24/2012 9:38:35 AM
Access Restriction Public


The .NET framework code within System.DirectoryServices.AccountManagement.CredentialValidator.Validate(string userName, string password) appears to corrupt object state during a specific usage pattern.
This can be worked around by forcing a SimpleBind on every call.
I was hoping to take advantage of the connection caching in this class, but after running into this issue and seeing the code in reflector, it looks fairly scary from a thread safety standpoint.

It appears that the code tries to communicate with the Ldap server over a secure port using non secure communications.
Sign in to post a comment.
Posted by Microsoft on 10/24/2012 at 11:45 PM
Thanks for your feedback.

We are rerouting this issue to the appropriate group within the Visual Studio Product Team for triage and resolution. These specialized experts will follow-up with your issue.
Posted by Microsoft on 10/24/2012 at 9:51 AM
Thank you for your feedback, we are currently reviewing the issue you have submitted. If this issue is urgent, please contact support directly(