Can't import certificate in Windows

[m.traeumner (Michael Träumner)]

NethServer Version: 7.7.1908
Module: Webinterface

Hi,
I need your help again, I can’t import the certificate in Windows. I tried at Windows 7 and Windows 10 to import it as root certificate, but next time I open the webinterface it asks again for the certificate. If I look at the message of the certificate it says:

The certificate is build for another site.
I also tried to generate a new one, but it’s the same problem.
Without the certificate CalDav-Synchronizer doesn’t work.
Thanks in advance
Kind regards
Michael

[mrmarkuz (Markus Neuberger)]

I tried to sync my SoGO with my Outlook 2013 with caldavsynchronizer and it worked without certificate issues. Why not use letsencrypt instead of importing certs?

[m.traeumner (Michael Träumner)]

Hi Markus,
thanks for your quick answer.

@mrmarkuz

worked without certificate issues

At the company I work for, I had to install the certificate too, but it wasn’t a problem to install it.

@mrmarkuz

Why not use letsencrypt instead of importing certs?

Yes, I think I will do this.
Thanks again.

[mrmarkuz (Markus Neuberger)]

I found a root ca install howto but I think requesting letsencrypt is much easier to install and maintain.

Chrome 70 and self-signed certs

Okay, I couldn’t just walk away. So… I enlisted the help of a couple of people still actively working with this stuff on a regular basis. None of us are network or security gurus, but we all do or used to do quite a bit of integration work. That is to say - we got it to work, but your mileage may vary. What follows is simply a distillation of the notes we kept while passing ideas around. This was developed using Windows 10 and Chrome 70 on the client side, with NethServer 6.10 running as the …

[m.traeumner (Michael Träumner)]

Hi,
thanks for your help again. I’ve found the solution at the manual, sometimes it helps to read it
https://docs.nethserver.org/en/v7/base_system.html#server-certificate

Note

To avoid problems while importing the certificate in Internet Explorer, the Common Name (CN) field should match the server FQDN.

After setting common name to FQDN, it works.