I have been beating my head against the wall. Where do I change the way SSL cert gets passed from amigopod to the controller so that secure.arubanetworks.com is not the ssl being used. I have the correct ssl's on amigopod and the controller, but for some reason I get a cert error for people who register.
the securelogin.arubanetworks.com is what is included in the Common Name (CN) on the SSL certificate installed on the controller for the internal captive portal server. If you replace the default server ceritificate on the controller with a new commerical or private certificate, the CN of this certificate should be used moving forward.
I did change the cert on the controller and amigopod. They come up correct when I go direct to those devices, but with guest auth and approval I get the secure.arubanetworks.com instead and have no idea where it is coming from.
When is you see the securlogon.arubanetworks.com name? Is it in the URL field? Is it the actual certificate being used?
Do I understand you correct if I say that I can request one public SSL certificate with a CN of securelogin.arubanetworks.com for all my controllers if I use the field show in the amigo-securelogon.jpg screenprint?
The controllers should all have a public cert for securelogin.arubanetworks.com by default.
Thanks for your reply. What I mean is, when I request one third party certificate for all my controllers (from Verisign, Comodo or whatsoever) does this one certificate work on all my controllers, and could this be accomplished by requesting the certificate for securelogin.arubanetworks.com.
At Aruba, we believe that the most dynamic customer experiences happen at the Edge. Our mission is to deliver innovative solutions that harness data at the Edge to drive powerful business outcomes.
© Copyright 2021 Hewlett Packard Enterprise Development LPAll Rights Reserved.