A
Andy
We are using Basic Authentication for our site. However, I could not
find any suitable Logout process except to close the window (the
solutions suggested on this site that point to old VB6 code which
requires creating an ActiveX object does not work correctly and I
don't want to create an ActiveX object).
The secured site is opened in a separate window. A link on the
non-secure site opens this window using window.open() javascript
function.
This is when the Basic Authentication is performed.
The problem is, because the popup browser has been spawned off an
existing browser window, the authentication details are still valid
when you close down the popup window but leave the original browser
window with the link open.
Hence, when you click on the link again, the popup window does not
request any authentication.
Does anyone know how to start a new browser process from ASP.NET so I
can get around this problem?
Your help will be greatly appreciated.
Thanks,
Andy.
find any suitable Logout process except to close the window (the
solutions suggested on this site that point to old VB6 code which
requires creating an ActiveX object does not work correctly and I
don't want to create an ActiveX object).
The secured site is opened in a separate window. A link on the
non-secure site opens this window using window.open() javascript
function.
This is when the Basic Authentication is performed.
The problem is, because the popup browser has been spawned off an
existing browser window, the authentication details are still valid
when you close down the popup window but leave the original browser
window with the link open.
Hence, when you click on the link again, the popup window does not
request any authentication.
Does anyone know how to start a new browser process from ASP.NET so I
can get around this problem?
Your help will be greatly appreciated.
Thanks,
Andy.