Security

I am trying to get OnBoard and Guest Redirect working on the same SSID. The typicaly deployment for OnBoard is to have employees connect to the guest network, get redirected to a Captive Portal in which they can then register their device. This works with a catch...

To allow access to the Google Play store to download the QuickConnect application, a whitelist neesds created and applied to the L3 Auth page for the captive portal redirect. When this Whitelist is applied, Android no longer detects that it is behind a captive portal and therefore does not automatically redirect the client to the portal. The user could open a browser and navigate to the web which would then redirect to the portal but this is less desirable.

The Guest network is used for both Guests as well as OnBoarding. Now when normal Guest connect to the network, they are not redirected. 

Anyone have a working solution to allow both and keep all functionality?

Thanks!

Issue with Play Store redirection in Android captive portal

Hi everyone,

Has anyone found a solution for this? I'm facing a similar issue. I've whitelisted all the necessary URLs to download an Android app from the Google Play Store. However, when I open the captive portal and click the link to download the app from the Play Store, I first get a pop-up saying "Continue Anyway via Browser." After selecting that option, it redirects to the same captive portal URL in the default browser. Only after clicking the Play Store link again am I able to access the Play Store.

This behavior is not ideal. Any suggestions for a better solution?

I am trying to get OnBoard and Guest Redirect working on the same SSID. The typicaly deployment for OnBoard is to have employees connect to the guest network, get redirected to a Captive Portal in which they can then register their device. This works with a catch...

To allow access to the Google Play store to download the QuickConnect application, a whitelist neesds created and applied to the L3 Auth page for the captive portal redirect. When this Whitelist is applied, Android no longer detects that it is behind a captive portal and therefore does not automatically redirect the client to the portal. The user could open a browser and navigate to the web which would then redirect to the portal but this is less desirable.

The Guest network is used for both Guests as well as OnBoarding. Now when normal Guest connect to the network, they are not redirected. 

Anyone have a working solution to allow both and keep all functionality?

Thanks!