Bug ER-1171: Guest Access redirect loop on 9.7.0.0.220, is the bug Keith refers to
which contains this following information. You can revert to 9.6.2 which has no
problem for SR ZDs, or use multiple certs with the real IPs of the two ZDs. - mwb
There are two workarounds for this problem:
1. If customer is happy to use 9.6.2, they can downgrade ZD to 9.6.2. Redirect with ZD management IP is working fine in 9.6.2
2. If customer wants to stay on 9.7, they can import different certificate on each ZD. For example ZD1 has FQDN zd1.wifi.com, ZD2 has FQDN zd2.wifi.com, also in DNS server, map zd1.wifi.com to ZD1 device IP address, map zd2.wifi.com to ZD2 device IP address. This setup will workaround management interface. But it requires two certificate, or wildcard certificate.
Wildcard Certificate Installation:
A wildcard certificate is a generic certificate that can be used for devices in a specific domain. This is useful for Smart Redundancy installations where you have two ZoneDirectors. You can purchase and install two certificates, or use a wildcard certificate.
When you try to import a wildcard certificate, the ZoneDirector will notify you that it does not have the matching private key. At this point, click on the "click here" link to import the private key. Once the private key is imported, try to import the certificate again. The ZoneDirector will prompt you for the host name. Enter the hostname and ensure that your DNS server is configured to resolve that name to the IP address of ZoneDirector.
Wildcard Certificates In Smart Redundancy With Captive Portals
In order to prevent redirect loops when deploying SSL certificates in a Smart Redundant configuration with Guest Access, Web Portal and Hotspot captive portals, use the following wildcard certificate procedure:
1. Purchase or generate a self-signed wildcard certificate such as *.acompany.com and install it on both ZoneDirectors in the Smart Redundant pair.
2. In DNS, add 3 host/IP entries similar to the following
◦ management.acompany.com; 192.168.0.100: This is the FQDN you wish to use for reaching the shared virtual management interface and is mapped to its configured IP address.
◦ primary-zd.acompany.com; 192.168.0.98: This is the FQDN for the primary ZD controller and its physical IP address.
◦ backup-zd.acompany.com; 192.168.0.99: This is the FQDN for the backup ZD controller and its physical IP address
3. When you import the wildcard certificate into the ZoneDirectors you will be prompted to enter the host name – make sure you use the same host name as you will advertise in DNS for that ZoneDirector (the default is the same configured ZoneDirector name).