Jump to content

Use a certificate chain for the self-signed certificate used for the web server

Recommended Posts

It would be nice to be rid of the constant prompting (well, "constant" maybe is a bit overstating it, but it's something that happens often enough to be noted and annoying) for accessing an "unsecure site" because of the self-signed certificate used by Polyglot. I also noticed a different certificate is used for the /WEB query like /WEB/sysconfig.txt vs what the Polyglot URLs use, not sure if/when it may change.

As I understand it, if you could at least use a certificate chain when creating the self-signed certificates, we'd have the option of trusting the self-signed root/parent used to generate the PG3 certificate each time it starts, thus avoiding having to go through the exercise of clicking through security warnings, which just feels tacky. :)


Any chance this could be done?

From what I was able to find online, there's plenty of examples to follow using openssl; not sure what Universal Devices currently is doing.

This had a healthy discussion on the subject:


Link to comment

@DSwallow why not just use HTTP? It won’t warn you that way.

I use: http://eisy.local:3000 

And never get a warning. Only if you’re using https would you. Since you’re internally accessing a device on the same network do you really need https? It’s just that browsers “default” to the https.

If you would like to pose this question directly to UDI it’s best to use the “Contact Us” method on their site. 

Link to comment
This topic is now closed to further replies.

  • Create New...