Important note about SSL VPN compatibility for 20.0 MR1 with EoL SFOS versions and UTM9 OS. Learn more in the release notes.

Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 3 replies
  • Subscribers 37 subscribers
  • Views 1777 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Authentication - Captive Portal works but frustrating

Cameron Barlow

Hi there, we have just moved over to the XG from a Lightspeed Rocket for our web filter and would like some advice about the captive portal auth method. 

At the moment, I can open my iPhone up, authenticate and browse the web fine.  However, when I walk around our site which has black spots for wifi etc, then I have to keep re authenticating.

Whilst I'm ok ish, we have staff who use their own laptops for teaching so when they are moving between rooms/buildings, they again have to re authenticate.

This behaviour differs with the Lightspeed Rocket we used to use as that used to tie the username with a device mac address and keep that connected for a pre defined period of time, even if you went offsite for several hours. 

Is there a way to setup the XG to behave in a similar way?

Thanks


Cameron



This thread was automatically locked due to age.
  • 0

    Hi Cameron,

     

    In Authentication -> Services -> Web policy actions for unauthenticated users (Captive Portal), you can disable keep alive and then set a user an inactivity timeout instead (I would suggest a low value like 15 mins to start). 

    This will work as long as your devices are not changing IP's when disconnects happen. 

  • 0 in reply to MasterRoshi

    Thanks so much for this suggestion.

    I will give it a try.

    Best wishes.

  • 0 in reply to MasterRoshi

    MasterRoshi said:

    Hi Cameron,

     

    In Authentication -> Services -> Web policy actions for unauthenticated users (Captive Portal), you can disable keep alive and then set a user an inactivity timeout instead (I would suggest a low value like 15 mins to start). 

    This will work as long as your devices are not changing IP's when disconnects happen. 

     

    I made the change to this in the early hours of this morning and it appears to be working well.  I shall slowly edge out the time over the next week or so.

     

    Many thanks.

     

Unfiltered HTML