Force a guest user to use a default page every time they close their browser.

  • 1
  • Question
  • Updated 3 years ago
Hi could someone tell me if it is possible to force a user, that uses a captive web portal to authenicate, to a default webpage every time they close their browser? Thanks for taking the time to answer this.
Photo of Dagger Phat

Dagger Phat

  • 3 Posts
  • 0 Reply Likes

Posted 3 years ago

  • 1
Photo of Rob Pritchard

Rob Pritchard

  • 86 Posts
  • 8 Reply Likes
Every time they close their browser or every time they open their browser?
Photo of Dagger Phat

Dagger Phat

  • 3 Posts
  • 0 Reply Likes
I guess It should be when they  open their browser.
Photo of Nick Lowe

Nick Lowe, Official Rep

  • 2491 Posts
  • 451 Reply Likes
Hi Dagger,

There is no conceptual way to do this after CWP authentication completes because there is no way to get reliable session state that applies in the context of the whole browser.

You could conceptually have a tab/window that you have to keep open to persist the CWP session via keep alive javascript means, but that would be really ugly. It also likely wouldn't work with mobile devices that aggressively cease executing tabs/windows that aren't in the foreground. It likely wouldn't be worth Aerohive implementing this therefore.

What it sounds like you are after is partially offered by an authenticated Web proxy (which would require secondary authentication to the CWP) via a PAC script and something like Squid:

https://en.wikipedia.org/wiki/Proxy_auto-config

http://www.squid-cache.org/

You could consider using this instead of using a CWP in the first place if all you intend to offer is Internet access while not permitting inter-station traffic.

There are significant complications with both provisioning this and HTTPS so this generally is not something that I would recommend exploring.

Nick
(Edited)
Photo of Dagger Phat

Dagger Phat

  • 3 Posts
  • 0 Reply Likes
Thanks for answering Nick.
We've thought of using a proxy server but i think this will be too much trouble for that little functionalty in the end. I think we'll end up lowering the registration period so the user gets the enforced page more often. :-)