I have users coming from a non-IIS server to an IIS server.
They log into the non-IIS server and click on a URL link to the IIS server resource. Only super users can see this link. I want to login these users transparently in the background without forcing them to authenticate again. So what I did was created an unprotected ASP page on the IIS server called autologin.asp and placed the following code on it
<%
Response.AddHeader "Authorization", "Basic c3VwZXJ1c2VyOnBhc3N3b3Jk"
Response.Redirect "%>
What I am trying to do here is add an authorization header so that for subsequent requests to protected files, the server knows that the user is already authenticated. Then I redirect the user to the secure file, however the browser still promts me with the basic authorization dialog.
Anybody have any ideas?
They log into the non-IIS server and click on a URL link to the IIS server resource. Only super users can see this link. I want to login these users transparently in the background without forcing them to authenticate again. So what I did was created an unprotected ASP page on the IIS server called autologin.asp and placed the following code on it
<%
Response.AddHeader "Authorization", "Basic c3VwZXJ1c2VyOnBhc3N3b3Jk"
Response.Redirect "%>
What I am trying to do here is add an authorization header so that for subsequent requests to protected files, the server knows that the user is already authenticated. Then I redirect the user to the secure file, however the browser still promts me with the basic authorization dialog.
Anybody have any ideas?
