we are facing the same issue!
The latest thing we tried was to save the certificate into a file and manually import it. But we have yet to see if this fixes the problem.
It appears that if you want a permanent exception for a certificate, you have to manually install the certificate by following the steps outlined here: https://superuser.com/questions/104146/add-permanent-ssl-certificate-exception-in-chrome-linux
A more convenient solution has been asked for from the development team.
Any update on a "more convenient solution"?
On MacOS, its as simple as going to https://localhost:9101/ssl_support and going to the site anyway. This adds the certificate to the Keychain.
Now the downside is the site I happen to implement this feature on through a custom plugin shows the site as 'Not Secure' simply because one of the certificates isn't properly validated according to Chrome's requirements.
Even if I manually set everything to 'Always Trust'.
Is it possible to fully validate a certificate without a third party?
2 of 2 people found this helpful
Just found this!
Enable that guy and chrome will 'Allow requests to localhost over HTTPS even when an invalid certificate is presented.'