8
1
I have a local REST-API service based on node/express and MongoDB.
I am planning to switch over from http to https.
The Clients are running on Windows Server 2012 R2 (Terminal-Server).
The REST-API is hosted via Docker on Ubuntu 16.04 LTS Server.
I know:
- I have to create a self signed certificate by using openSSL on the server hosting the API
- Browsers have problems accepting self signed certificates
My Question:
- Is it possible that Clients (Chrome) will accept the HTTPS connection using a self signed certificate?
Thanks for your reply, I had an problem with windows not accepting the import of the certificate. Its now fixed :) source: https://superuser.com/questions/145394/windows-7-will-not-install-a-root-certificate
– oldmayn – 2018-02-20T10:49:53.2801Down vote, because these instructions only apply to legacy google-chrome. Somewhere before version 67 they completely disabled all of this self-signing functionality because illegal websites used this mechanism to distribute illegal data and datums. Your choices for now are to put up with no encryption, or to pay money to the certificate authorities so that the powers that be authorize you to have a website that works through the internet. Don't-be-evil has transformed into "just-a-little-bit-evil". – Eric Leschinski – 2018-09-24T16:32:54.737
1@EricLeschinski: Thanks for the update. IMHO, if an answer is outdated, it should be edited, not downvoted - it's stil correct, just old. – sleske – 2018-09-25T07:40:23.687
2@EricLeschinski: And for the record, I just tested this with current Chrome (V69 on Windows), and it does work for me. However, you need to restart Chrome after importing the cert. Answer edited. – sleske – 2018-09-25T07:42:35.893
1Thank you @sieske. RESTART CHROME was the thing that made it all work. – Julian – 2018-11-02T13:43:45.520