IP Based Authentication for Clientless SSL

Let me just start off by saying: Yes, I know this is inherently insecure.

That being said, can an ASA appliance be coerced into opening up a clientless SSL connection based solely on source IP?

A related question is whether or not the ASA can forward a username\password to a destination server without the user entering it at the ASA?

Here's the situation: I need to set up a way for a client to be able to come to the ASA and, based on source IP, be forwarded to a Virtual Desktop Interface. I know that piece is easy but I need to attach credentials that Windows Active Directory will accept.

Replies

1. An ASA cannot use the source IP address directly for authentication, however using either DAP or NAC you can control which tunnel group a particular client will connect to based on the source IP address. For more information regarding DAP, please refer to the following link:

You could also try using Digital certificates. If the certificate contains the source IP address in the CN then it will use the IP address to authenticate the client. For more information on using digital certificates for authentication you can refer to the following link: