Recently I tried installing WebVPN usability onto a Cisco ASA firewall. When trying to login I received the following error:
Clientless (browser) SSL VPN access is not allowed
That’s odd. I’m the administrator. I WANT to allow this. It’s my goal to allow this! Also, I wish Cisco would have consistency for this type of VPN. Is it “Clientless (browser) SSL VPN” or “WebVPN” or “SSL VPN” or “Clientless VPN”? Make up your mind!
Perhaps the logs give us more of a clue. It said:
May 22 2013 17:20:42: %ASA-4-722050: Group <GP-WEBVPN> User <test-user> IP <220.127.116.11> Session terminated: SVC not enabled for the user
This immediately became a battle with licensing. A quick show version gives me the following details:
It appears we have AnyConnect Premium Peer license applied to this firewall. But is it in use?
Doh! It appears
anyconnect-essentials is enabled! Here’s the reason why this is a problem.
Anyconnect-essentials does NOT support WebVPN. You must have Anyconnect Premium enabled to use WebVPN. It’s confusing because the way the licensing works is that You can either have essentials on or not. If you don’t then you have premium on. Either way you cannot have both at the same time. In order to make this WebVPN script work I had to say
no anyconnect-essentials which enables the premium peers. This brought us from 250 possible simultaneous VPN sessions down to 50.
To learn more about AnyConnect license (and why anyconnect-essentials doesn’t allow you to use WebVPN) see my post about it.