Hi,

 

We are trying to migrate this tool with our current password reset tool (ASP.NET C#) on our website. Our goal is to migrate ALL of our users (several thousand) to the ADSS tool. When a user goes through out current password recovery tool, we'd like to first query the ADSS database to see if the user has answered 3 security questions. If they have NOT, we'd like to have them continue through our current recovery tool. At the end, once they reset their password, we want to redirect them to the ADSS recovery tool. If the user HAS entered 3 securty questions, we'd like to redirect them to the password recovery page for the ADSS tool.

 

Here's what we got so far:

 

Upon going through our current password reset tool, we are currently querying the ADSS database to check if the user has entered 3 security questions (this works perfect). We made an exact copy of the form used to submit the user's username, on the FORGOT YOUR PASSWORD page ( http://domain/accounts/Reset) so that the user lands on the security questions page ( http://domain/accounts/ValidateUser) without having to reenter their username.

 

The issue:

 

When you open up IE for the first time and you enter our current recovery tool AND you have 3 questions answered, and we do an automatic form submission to the ValidateUser page the results come back as a blank page. If you were to navigate to the home page ( http://domain/showLogin.cc?logoutFromSSO=true) on the same window (<--important) and click on FORGOT YOUR PASSWORD without entering any information, then naviagate back to our current recovery tool and submit again, when our tool finds the 3 answered questions and submits the form to ValidateUser page, it works perfect! It's almost as if , you have to visit the page FIRST (maybe something in the backend is happeneing that we do not know of) which allows the user to continue on.

 

Currently, we are redirecting the user to the Reset page forcing the user to enter their username again. For the convenience of our users, we'd really like to bypass this situation.

 

Is this a bug? Is this by design? Is there a workaround? Is there an API available we can use to accomplish our requirements?

 

Thanks in advanced for your support.