TheNephalim
Programmer
Hello,
I'm in a bit of a quandry. We have a website on a Win 2k3 server. As part of the registration process, I have a dll running that will map their certificate with their Active Directory account. The process worked well on our Windows 2K server, and, after some modifications for the fact that 2k3 does everything in Unicode, works well on the new OS with one exception.
When a user's certificate was successfully mapped in 2K to their Active Directory account, they were instantly able to gain access to any section of the website that required authentication. Now what happens is that a user will get prompted by an challenge requiring user name and password, which the user does not know. If the user closes out their browser, then enters the website again, they are not challenged and everything works as it should.
Does anyone have any explanation for why this occurs? Is there something that I can do to recreate what I had on Win 2K? If not, I do have a work around where we tell the users that they will need to close out their browser and enter the website again, but this is not something that I would like for them to have to do.
Thanks for any assistance.
Sincerely,
Robert Eberhart
I'm in a bit of a quandry. We have a website on a Win 2k3 server. As part of the registration process, I have a dll running that will map their certificate with their Active Directory account. The process worked well on our Windows 2K server, and, after some modifications for the fact that 2k3 does everything in Unicode, works well on the new OS with one exception.
When a user's certificate was successfully mapped in 2K to their Active Directory account, they were instantly able to gain access to any section of the website that required authentication. Now what happens is that a user will get prompted by an challenge requiring user name and password, which the user does not know. If the user closes out their browser, then enters the website again, they are not challenged and everything works as it should.
Does anyone have any explanation for why this occurs? Is there something that I can do to recreate what I had on Win 2K? If not, I do have a work around where we tell the users that they will need to close out their browser and enter the website again, but this is not something that I would like for them to have to do.
Thanks for any assistance.
Sincerely,
Robert Eberhart