0

Use Certificates signed by common CA for Web-UI

Matthias Klein

February 11, 2023 23:07

None

Follow

Right now, accessing the Web UI of the PBX shows a "this connection is not secure" warning in the browser because the Certificate can't be validated.

Sure, it's not a critical thing, but just get a signed Certificate, please. If not for any other reason but to make your PBX look more professional.

• Facebook
• Twitter
• LinkedIn

2 comments

• 1
  
  Sandro Sartori February 14, 2023 08:40

  Hi Matthias

  You can upload your own certificate to PBX

  On P-Series in "Security - Security Settings - Certificates" and then you have to choose it for HTTPS in "System - Network - WebServer - HTTPS Certificate"

  Or you can purchase the license for Enterprise Plan which includes "Remote Access Service" with "Custom PBX Domain Name (FQDN)"
  
  I hope to be helpful
  bye

• 0
  
  Matthias Klein February 14, 2023 13:53

  Thank you. Yes, I am aware that many things can be done manually (password changes, certificate changes, etc.) - but my personal opinion is that the PBX should include / do many of them automatically and by default.

  • Right now, there is no signed cert by default - only if the admin uploads it manually
  • Right now, Yeastar does not automatically change the phone passwords when adopting phones - this has to be done manually
  • Right now, Yeastar does not automatically keep the firmware of phones up-to-date - that has to be done manually

  And so forth - the list continues.

  Some of those items are security best practices - and other PBXs follow them by default. Yeastar doesn't. And that causes not only a security risk but also annoying side effects to the user.