Majority of our users with a personal device are having trouble connecting to our Clientless portal to download the Anyconnect Client. Its either a Java or ActiveX issue most of the time. We are only using the Clientless portal to provide the user to download the client, that’s it.
These personal devices are not part of our corporate network so we don’t have a way to push by GPO or whatever.
Can we put the Anyconnect Client windows executable on our public facing web server instead of the clientless portal? is there legality issues with this?
Have you considered setting up a connection profile for full-tunnel SSL VPN (non-clientless)? That might help.
I can't speak to the legality / EULA compliance of putting the full client msi package out on your public server. I'd think at least some due diligence to restrict it's use to authorized clients would be in order - if nothing else to prevent you from being a known location for anyone in the world do download the software. Something like an unpublished link with instructions sent out via e-mail.
We have configured the outside and inside Interface with official ipv6 adresses, set a default route on outside Interface to our router, we also have definied a rule , which also gets hits, to permit tcp from inside Interface to any6.
In Syslog I also se...