I was setting up a PIX last week for VPN, no problem there, but the customer also wanted to use SSL direct through the firewall, and we ended up with this problem. I think it may be a browser issue, but that is outside my knowledege area, so I'm asking for help here.
My customers has a server that supports SSL connections, and I configured the PIX to allow an external user HTTPS access to this server, although relatively insecure that worked fine.
To improve security I set up the PIX to provide cut-through proxy support, using this the user is presented with a username/password dialogue box when the initial connection is made, this is authenticated against his Radius server, then the connection is passed through to the server. This is SSL from the user through the firewall to the server.
The problem we saw occurred on the second login attempt, the original username and password requested by the PIX are cached by the browser, so hit OK and the connection goes straight through the PIX! Can the SSL connection modify this behaviour somehow, so when the connection is made onto the server the browser dumps the cached credentials?
Andy
My customers has a server that supports SSL connections, and I configured the PIX to allow an external user HTTPS access to this server, although relatively insecure that worked fine.
To improve security I set up the PIX to provide cut-through proxy support, using this the user is presented with a username/password dialogue box when the initial connection is made, this is authenticated against his Radius server, then the connection is passed through to the server. This is SSL from the user through the firewall to the server.
The problem we saw occurred on the second login attempt, the original username and password requested by the PIX are cached by the browser, so hit OK and the connection goes straight through the PIX! Can the SSL connection modify this behaviour somehow, so when the connection is made onto the server the browser dumps the cached credentials?
Andy