Allow overriding captive portal redirect URL as a hidden POST param

stuartst

When using external captive portal Nebula only offers 2 redirect options:

• Stay on Captive portal authenticated successfully page, and;
• To promotion URL

All other vendors providing captive portal allow supplying a redirect URL parameter that can override the default redirect value configured on the controller.

Our captive portal solution displays offers/ads as a Call To Action that should redirect the user to the landing page specific to that offer/ad. With the current functionality it is not possible to override the redirect URL by passing a "redirect_url" hidden form parameter.

The feature request is to allow passing an optional "redirect_url" hidden form param that can be set if required that will override the configured promotion URL on the Nebula cloud configuration. If the value is not specified the redirect can fallback to the configured promotion URL on the Nebula cloud configuration.

Zyxel_Kay

Hi @stuartst

Currently, the 'To promotion URL' option allows users to specify the URL to which they are redirected after a successful login. You can set your 'redirect_url' in this option without any restrictions on the URL link.

Your request for an additional 'redirect_url' parameter can be achieved by setting your desired redirect URL directly in the 'To promotion URL' field, rather than adding another option to this feature.

stuartst

Hi Kay,

Thanks, but this is not what I want to achieve. I want to be able to dynamically override the Nebula configured redirect URL on a per offer/ad basis from within my captive portal page.

All over Wi-Fi vendors who support captive portal provide this in the form of an option similar to "Redirect to the original URL the user browsed to". This exposes a "Redirect URL" param to the captive portal as a query string param. This URL is then added as a query string param or hidden POST form param on the authentication URL so that can be overridden to change the final destination for the user.

Cisco:
Captive portal URL: https://my-captive-portal.com/?switch_url=http://1.1.1.1/login.html
&ap_mac=11:22:33:44:55:66&client_mac=66:55:44:33:22:11&wlan=
Test&redirect=https://my-original-url.com

I then post to the controller with a hidden form param of redirectUrl = http://my-new-url.com and it will redirect the user to that URL on successfully login instead.

Meraki:
Captive portal URL: https://my-captive-portal.com/?base_grant_
url=https%00%00%00n00.meraki.com%2Fsplash%2Fgrant&user_continue_
url=http%3A%2F%2Fgoogle.com%2F&node_mac=00:18:0a:xx:xx:xx&client_
ip=10.128.128.120&client_mac=xx:xx:xx:xx:xx:xx

I then redirect to the base_grant_url and add query param continue_url = http://my-new-url.com and it will redirect the user to that URL on successfully login instead.

Ruckus:
Captive portal URL: http://yourwebsite.com/?sip=192.0.2.1&mac=112233445566&client_mac=665544332211&uip=192.168.100.1&url=http%3A%2F%2Fgoogle.com%2F

I then redirect to the sip URL and override the query param url = http://my-new-url.com and it will redirect the user to that URL on successfully login instead.

And so on for every other Wi-Fi vendor…

Can Zyxel not add the ability for us to provide an optional redirect URL to the authentication endpoint URL (e.g. http://2.2.2.2/cgi-bin/Clicktocontinue.cgi, either as a hidden post param or query string param) so that it can bypass the original Nebula configured value?

Zyxel_Kay

Hi @stuartst

Thank you for sharing the additional information with us. We will be monitoring the votes and comments as part of our evaluation process for this feature.

If anyone likes this idea, please show your support by leaving a comment or voting for it.