Quantcast
Channel: Untangle Forums
Viewing all articles
Browse latest Browse all 5188

Closing an authenticated Browser not unauthentication/closing the session in CP

$
0
0
After closing an authenticated Web Browser through Captive Portal on the Client's Host, Captive Portal Status is still showing the Client's Host as active session ("logged in"). This is very annoying because the same Client Host can open up a new Web Browser without authentication required. I don't understand why Captive Portal cannot recognize a "closed" Web Browser on the Client's Host? This concept works fine with my current Squid3 Proxy setup which I would like to replace with Untangle. Is there a work-around solution? Thank you.

Viewing all articles
Browse latest Browse all 5188

Trending Articles