O
Oran
I am trying to integrate an application into our extranets.
The extranet technology has its own authentication system requiring a domain user but uses anonymous authentication (from the perspective of IIS). I can get the username/password, but IIS is not aware of the user.
The application I am trying to integrate (to get the features I want) relies on either basic or NTLM authentication. The sites use SSL, so basic authentication is fine. Both applications live on the same server.
I want to automatically authenticate the user in the second app. Any ideas? I have a few, but I don't know how to implement them.
One idea is to find a way to forward/redirect the basic authentication information to the secondary application. This would be easier (and less secure) if IE6 still supported the "http://user:pwd@server/" syntax... I could construct the authorization request-header myself on the server, but how would I convince browsers to send it? It should work with recent IE and NS browsers.
The extranet technology has its own authentication system requiring a domain user but uses anonymous authentication (from the perspective of IIS). I can get the username/password, but IIS is not aware of the user.
The application I am trying to integrate (to get the features I want) relies on either basic or NTLM authentication. The sites use SSL, so basic authentication is fine. Both applications live on the same server.
I want to automatically authenticate the user in the second app. Any ideas? I have a few, but I don't know how to implement them.
One idea is to find a way to forward/redirect the basic authentication information to the secondary application. This would be easier (and less secure) if IE6 still supported the "http://user:pwd@server/" syntax... I could construct the authorization request-header myself on the server, but how would I convince browsers to send it? It should work with recent IE and NS browsers.