Did you determine what was causing this problem? I get the exact same error message you mention when tryhing to login via SSL. I had the SSL connection working on my ASA earlier, and after playing some with the Cisco Secure Desktop I can't get it to authenticate me. I was hoping you had some insight into this that might get me going again.
OK guys so here is what I got from TAC. I have been using the "Group Lock" Option on all of my users. Up until 8.0(3) SSL VPN ignored "Group Lock" and place all uses in the defaultWeb instance if they did not specify a Group via the drop down. So all I had to do to get my authentication working again was to enable the drop down on the login portal for SSL VPN. I then created alias names for all of my tunnels that are allowed to SSL VPN so I wasn't exposing the realy tunnel group name. This not only fixed my issue but helped me understand why I was having so much trouble with custom SSL VPN pages for users and groups. The Authentication has no interaction with tunnel group other than to validate that you are connected to the tunnel group you are locked to. If you aren't as in the case with default SSL instance when you don't specify in the drop down it just dumps the Auth request.
Login to the FXOS chassis manager.
Direct your browser to https://hostname/, and log-in using the user-name and password.
Go to Help > About and check the current version:
Check the current version availa...
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...