Hello >> We are now trying to install our own SSL certificate. Right now when >> using Chrome, we receive a WARNING because of the selfsign cert. >> Do you have any tutorial to help us on that ?
I am assuming that you have already 1. created your own CA, 2. created a certificate, 3. created a signing request and 4. signed the certificate with your CA. If you have done all that, you can get rid of the warning by importing your CA certificate in all browsers that will use openmeeting. In production that's not feasible at all, and it is also not worth it. You can get your certificate commercialy signed for under USD 10 per year (even down to under USD 5 per year if you pay for four or five years at once), and then the CA certificate is already in all browsers and you get rid of all the hassle and the ensuing support nightmare. Note: some SSL vendors will include www.domain.tld for free if you request domain.tld but not vice versa, others will charge you separately for each. It's worth spending five-ten minutes researching before ordering. And then you have completely free certifcates from https://letsencrypt.org/ , but they come with their own set of question marks. Cheers, Z
