How do I work with a self-signed certificate in Chrome Apps?

Question

I am developing a Chrome application that connects to the server via SSL. Of course, the certificate is self-signed.

In the Chrome browser, this is not a problem because Chrome opens the security warning page. If the user decides to continue working on the website, he goes to the remote page. However, in Chrome Apps, it does not give such a warning page about whether to continue or not. Instead, a connection error is thrown in the console.

To work around this problem, the user must connect to the page in the browser once and accept the certificate, and then he can continue to work in Chrome applications.

I’m wondering how to directly resolve this issue in Chrome Apps?

Answer 1

If the server uses a self-signed certificate, then you can do nothing. There are two other ways that require changing the certificate on the server side and depending on these changes, the user may or may not have to make some settings in the browser

• Update the server with a trusted CA certificate. This does not require any settings from the user. Examples of trusted CAs are GoDaddy, VeriSign, etc. You can check the list of trusted CAs in chrome: // parameters → HTTPS / SSL → Certificate management → Trusted root certificate authorities

• , CA. , / / , , :// → HTTPS/SSL → → , " ". , SSL .

, , , , , Chrome Apps

Answer 2

http://www.startssl.com/?app=1 SSL. , , . http:, .