09-15-2011 02:13 AM
I'm trying to get a webvpn setup to run with two ASAs which are cascaded. Each ASA requires the user to login to webvpn. Practically, this means that you log in to the first ASA, which, upon successful login, should automatically divert you to the webvpn login screen of the cascaded ASA with a 'homepage value https://<ip>' command.
This doesn't work properly as the first ASA won't ever present you with the webvpn login of the second ASA, yet instead you'll only see the login of the first ASA again. I suspect this might have something to do with cookies or the way ASAs compute the special URL they present the user's browser...?
By the way, any other HTTPS web service works properly when referenced as a homepage, it just won't work with a second ASA. Also, directly logging in to the second ASA works without problems.
Has anybody got an idea how to solve this?
Thanks
Toni
Solved! Go to Solution.
10-03-2011 12:50 AM
Hi Toni,
this is not supported scenario (clientless through clientless)
regards,
Rami
10-03-2011 12:50 AM
Hi Toni,
this is not supported scenario (clientless through clientless)
regards,
Rami
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide