HTTPS unsecure connection message with self-signed certificates
Hello, We are manufacturers of networking devices. As most networking devices, ours can be configured by navigating to the default gateway IP address via the browser. W… (kàsi)
Hello,
We are manufacturers of networking devices.
As most networking devices, ours can be configured by navigating to the default gateway IP address via the browser. With the rise of security awareness, various regulations are forbidding the usage of HTTP. This is bothersome to us, as connecting to our devices via HTTPS and our self-signed sertificates will always throw an error of an unsecure connection to the end user. We understand the technical reasoning for this and that users are able to ignore the message, but this does impact our user experience and it may even discourage users from using our devices.
As these regulations will be impacting networking devices globally, we want to ask you if there are any workarounds for the self-signed sertificate "unsecure connection" message. Perhaps there is an argument that can be set, or an ongoing effort from browser vendors to assist networking device manufacturers with this.
Any information or help is appreciated.
Thank you.