This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Owned SSL Cert not working in captive portal SFOS 19.0.0 GA-Build31

Captive portal in version SFOS 19.0.0 GA-Build31 is not using specified certificate as admin portal.

Captive portal is using SOPHOS cert which is not correct in my setup. See below images.

Have tried fresh re-install, upgrade removing and re-adding the cert an CA detail - not working.



This thread was automatically locked due to age.
Parents
  • I am having the exact same issue, this was working correctly before the update to SFOS 19.0.0 GA-Build31. The admin page and user portal are using the correct certificate selected under Admin console and end-user interaction, put the captive portal (port 8090) is using the appliance certificate instead.

  • Hello ,

    Can you just double check if the default cert from certificate > certificate authorities in installed in the client machine and has the details filled in properly after you updated the firmware ? 

    Thanks & Regards,
    _______________________________________________________________

    Vivek Jagad | Technical Account Manager 3 | Cyber Security Evolved


    Sophos Community | Product Documentation | Sophos Techvids | SMS
    If a post solves your question please use the 'Verify Answer' button.

  • Hi Vivek

    The certificate is not on the client machine as this is used to ask for authentication on BYOD mobiles which do not have the client cert installed. We are using a LetsEncrypt certificate so that the mobiles are not presented with an invalid certificate. This worked perfectly in 18.5 as the mobiles were presented the captive portal with the LetsEncrypt certificate which they will trust by default.

    The admin page and user page both present the LetsEncrypt cert as expected.

    EDIT: I have reverted back to SFOS 18.5.3 MR-3-Build408 and the expected behaviour has returned (Captive portal is using LetsEncrypt cert as expected).

  • Simon, same experience. One migration to version 19 the Sectigo cert is used for Admin and user portabl. Captive portal is using appliance certificate which is not correct.

    This is clearly a bug that on upgrade the captive portal is broken. I've rolled back to 18.3 cannot use 19 with this issue. 

Reply
  • Simon, same experience. One migration to version 19 the Sectigo cert is used for Admin and user portabl. Captive portal is using appliance certificate which is not correct.

    This is clearly a bug that on upgrade the captive portal is broken. I've rolled back to 18.3 cannot use 19 with this issue. 

Children