Ticket #3371 (accepted defect)
Captive Portal's SSL
|Reported by:||development@…||Owned by:||cperez@…|
|Severity:||normal||Keywords:||ssl ca captiveportal|
The Captive Portal doesn't have a Service Certificate listed under the Certificate Authority and the certificate used has a bad CN ("eBox Server") which causes SSL errors clientside. Also, it addresses the captive portal using the server's IP address, can it be addressed using a specified hostname instead? This would reduce problems when Captive Portal's SSL is functioning to avoid CN mismatch issues and create a better user experience browser-side.
At the moment, captive portal is quite clunky to use clientside with these problems in a real environment unless you manually issue and change the certificates and redirections.
- Owner changed from jacalvo@… to cperez@…
- Component changed from base to captiveportal