Guest access – Ruckus ZoneDirector
In this topic, you will learn how to configure Ruckus ZoneDirector to work together with the Portnox™ Cloud captive portal for guest user authentication.
Before you begin configuring your access point, you must configure the guest network in Portnox Cloud and note down the values of the fields: IP (for walled garden), Captive Portal URL, and Shared secret.
Important:
To run a captive portal in Ruckus ZoneDirector, you must install Portnox LDAP Broker on a physical or virtual Windows machine that is in the same subnet as your controller. AD
Broker is necessary for this setup because it serves as the channel of communication between Portnox Cloud and the
ZoneDirector API.
Important:
This guide gives general instructions for integrating Portnox Cloud with specific
third-party devices. We try to provide useful examples for common models, but settings can differ between manufacturers,
models, and environments. Because of this, we cannot guarantee these steps will work in every case. For questions or
problems with RADIUS setup – which is an industry standard and not specific to Portnox – or with device-specific settings
and troubleshooting, we recommend checking the device manufacturer’s documentation and contacting their support team.
Portnox Support can help when possible, but detailed setup of third-party devices is usually best handled by the
manufacturer. We also recommend updating your NAS device firmware to the latest version, as old firmware can cause
issues.
Important:
All values in this configuration are examples. Make sure to adjust the configuration to
your individual profile names, RADIUS server addresses, ports, and keys by replacing the values that are presented as
underlined italics.
This configuration was tested on Ruckus ZoneDirector ZD1200.














