Using Aerohive with an external BYOD solution

  • 1
  • Question
  • Updated 3 years ago
We are trying to setup a BYOD solution using Aerohive APs.

To create some context, let me explain what I mean with "BYOD" Solution.

The idea of a BYOD solution is to on board user owned devices to a Secure 802.1X SSID.

BYOD solutions rely on the user initially connecting to an Open "Start Here" SSID. 

The AP broadcasting this SSID is setup to redirect all HTTP/HTTPS traffic to a specific URL.

For a User this means that when they open a browser on their device and try to "google", the browser traffic is captured and redirected to this URL. 

This URL is running BYOD software that will show a welcome screen to the user, then detect the device and deploy an OS specific BYOD client. 

This BYOD client, when run, then configures and connects the device to the Secure SSID. 

These BYOD clients however often rely on external services during the onboarding process, things like Google play, Amazon Kindle store, Chrome Webstore and so on. 

Currently we are looking at how to achieve the above scenario with Aerohive. 

Cisco, Aruba, Ruckus all support this through their Captive Portal functionality, and it looks like there is the option in Aerohive to setup a similar Captive Portal "redirect URL", however it looks like this will redirect everything except for the IP of the redirect URL (which works fine when using this together with simple guest access). This is enough to kick of the BYOD process and redirect the User to the BYOD URL, but the BYOD clients cannot run correctly as any HTTP/HTTPS request to the required external services is redirected.

The other vendors allow you to base the Captive Portal Redirect URL on an ACL which allows you to achieve the above, so we are wondering if this is available in Aerohive. 

Or if someone has any other ideas on how to achieve the above I would be interested to hear them.
Photo of Tom

Tom

  • 1 Post
  • 0 Reply Likes

Posted 3 years ago

  • 1

There are no replies.