It's a good thought but we already have a Guest regristration process, and honestly I'm not certain how captive portal would play into the "continue" function. I ended up opening a ticket and found the issue. It makes sense, but I didn't realize SSL interception was necessary for the "continue" function. For our non-corporate networks, BYOD, we obvious can't intercept that traffic. Since the sites I was trying to force through continue were SSL I was getting SSL protocol errors in the web browser. I guess there are some other settings that were required which I already had configured except one. Via CLI I needed: ssl-decrypt url-proxy yes This allows any website to be processed for interception (only for which allows the continue function to work. The one caveate to this is BYOD get the MITM cert error because we're using an internally signed cert for interception and they don't have our root cert on their device. However in our case that's fine, because we'd rather make them click to continue. --EDIT-- "continue" breaks applications. So for instance you want to continue Facebook, well doing so breaks the application on a smartphone. So just an FYI for someone trying to do so on BYOD.
... View more
