Important Notice: Our web hosting provider recently started charging us for additional visits, which was unexpected. In response, we're seeking donations. Depending on the situation, we may explore different monetization options for our Community and Expert Contributors. It's crucial to provide more returns for their expertise and offer more Expert Validated Answers or AI Validated Answers. Learn more about our hosting issue here.

After AnyConnect weblaunch why do we keep the browser open after AnyConnect session establishes?

April 26, 2017anyconnect browser establishes session weblaunch

0

Posted

After AnyConnect weblaunch why do we keep the browser open after AnyConnect session establishes?

1 Answer

0

Posted

A. A couple of reasons: • A matter of convenience to allow the user continuing the use of the Clienltess portal even after the AnyConnect tunnel/session is operational. • Current browsers implement tabbed windows, or mutiple windows from a single process, therefore the Anyconnect agent killing of the browser process causes the user to lose all tabs/windows in that process, not just the one for the Clientless portal. Note:Currently there is no capability to allow the browser process to be killed when Anyconnect tunnel establishes. SVC 1.x did support this capability .