ChangeQA process gets loaded in environment where ADAM is not on SharePoint box


This occurs because FindUser throws an exception because it is called as the currently logged in user using Windows integrated authentication for an ADAM user. This causes an exception to be thrown which is not handled. SharePoint displays an error that the user could not login with the current userid and password.
We must revert to the server user before doing these FindUser calls. These calls seem to be made when the system is checking for the reset question to be the sentinel value, for the password having been just generated, or for the password getting close to expiring.
Closed Feb 18, 2008 at 9:21 PM by KevinE
Unclear. This is describing the underlying cause of a couple issues. Closing and tracking the issues seperatley.


wrote Feb 18, 2008 at 4:35 PM

I have no idea what this bug is about.

wrote Feb 18, 2008 at 9:21 PM

wrote Feb 1, 2013 at 1:56 AM

wrote May 13, 2013 at 5:28 PM