Subject Alternate Name for DNS in SSL CertificateDNS

Hi,

When I install new eDirectory 9.3 servers the default certificates (SSL CertificateDNS) doesn't get the DNS name added as Subject Alternate Name (SAN). Only the IP is added as SAN.

Since this certificate is used for LDAPS, it causes other issues such as IDApps and IDConsole won't connect using the servers DNS name. I can of course work around this with a custom certificate where I specify the DNS name as a Subject Alternate Name and use that for LDAPS, but I'd really like to figure out why the default certificates doesn't get the SAN automatically. I can also use IP from IDApps and IDConsole, but that is not optimal...

I am in a sandbox environment, so it could be an issue in my environment. I do however configured a DNS with both A and PTR records, so it should be possible to autodiscover the DNS name.

If anyone has insights on this, I would appreciate it.

Thank you!

Best regards

Marcus

Labels:

LDAP Proxy
Parents Reply Children
  • 0 in reply to   

    Hi,

    Sorry for being unclear.

    I see I had some faults in my original post (updated now). The case was new installation of eDirectory servers, not repair of default certificates.

    If the hosts file on the engine server is as stated previously, the default certificates includes DNS as SAN. Since this is during installation of servers, Identity Console is not involved.

    However, if I later repair the default certificates using Identity Console, I loose DNS in SAN again.

    If I delete the default certificates and recreate them using "ndsconfig upgrade", they are again created with DNS in SAN.

    Best regards

    Marcus