When creating a certificate request (.csr) from the ESG and submitting it to our Microsoft Standalone CA, the certificate issued doesn't contain a Subject Alternative Name (SAN).
The ESG also shows the Cert as "Missing Chainfile Untrusted" (under Secure Administration) however when you view the Cert in Chrome or IE, the Cert path is valid and the Cert is reported as OK by both browsers.
Since Chrome will only trust Certs with SAN, I'm trying to generate a CSR with SAN info to submit to our CA.
Is this expected or is there a configuration issue in our ESG somewhere?
We also use the Message Archiver appliance, and CSR generated from that device contains the SAN in the request.
Any help is appreciated.