Security

last person joined: yesterday 

Forum to discuss Enterprise security using HPE Aruba Networking NAC solutions (ClearPass), Introspect, VIA, 360 Security Exchange, Extensions, and Policy Enforcement Firewall (PEF).
Expand all | Collapse all

safari can't access guest logon page

This thread has been viewed 1 times
  • 1.  safari can't access guest logon page

    Posted Oct 30, 2014 10:56 PM

    Guest ssid use captive portal certification ,when user use MAC's safari ,it shows " can not create security connection to securelogin.arubanetworks.com ,but when use google chrome ,it works.

     

    Does anybody encounter samilar problem?



  • 2.  RE: safari can't access guest logon page

    EMPLOYEE
    Posted Oct 31, 2014 01:41 AM
    What OS is the MAC running?

    What version of CPPM?


  • 3.  RE: safari can't access guest logon page

    Posted Oct 31, 2014 02:21 AM

    OS version: 10.9.4

     authentication use internal db in controller.



  • 4.  RE: safari can't access guest logon page

    EMPLOYEE
    Posted Oct 31, 2014 06:36 AM

    Colin Wang,

     

    Does Safari give any additional details?

     

    The built-in certificate on the controller is only meant as a proof of concept and should be replaced with a public SSL server certificate so that users can avoid those errors.



  • 5.  RE: safari can't access guest logon page

    Posted Nov 02, 2014 08:52 PM

    Detail info is showed in picture attached.

    how to ignore certificate check process in safari?

    when I use http authentication ,it works.

    IMG_2076.JPG



  • 6.  RE: safari can't access guest logon page
    Best Answer

    EMPLOYEE
    Posted Nov 02, 2014 09:49 PM
    Like Colin mentioned you will need to get a publicly signed cert and replace the securelogin cert on the controller if you want to use https.

    The only other option is you could export the cert and manually import it into the device but you will need to do that for everyone.

    A default Cert should only be a placeholder for a true cert. In all of the documents it states that you should replace the default cert for a true https connection.

    Would you want to connect to a website that gave you a cert warning. I know I wouldn't. :)