03-13-2014 09:58 AM
03-13-2014 10:17 AM
The captive portal will use the CN of the certificate that you have selected for the controller. If you use the DNS name of your controller, you can use the cert for both Mgmt UI and captive portal without getting SSL errors.
03-13-2014 10:30 AM
Right, and there in lies the problem (pgh-local.mycompany.int). We have an internal domain that is .int and since .int is actually a usable external DNS suffix I can't get a cert from a public CA or whatever Thawte and Go Daddy are...
03-13-2014 10:33 AM
03-13-2014 10:41 AM
"Do you have a public facing domain name though? You could always do a
generic wireless.domain.com just for the captive portal. The DNS name
doesn't have to actually exist."
i mean if I use wireless.mydomain.com don't I need a corresponding "a" record in DNS so the client can find the captive portal?
03-13-2014 10:45 AM