Chrome stopped supporting Common Name matching in the latest release 58 which dropped in the last week or so. This would cause the error you referenced below. Looks like it now only supports names in the subjectAlternativeName field of the cert.
Hope this assists Nathan On Thursday, April 27, 2017, Scott Voll <svoll.v...@gmail.com> wrote: > OK, as of yesterday I started having reports of users in Chrome and > Firefox getting an error connecting to the Finesse webpage. > > Looking at the cert It's sha2 but I get Not secure in FF and not private > in Chrome. > > Chome complains of NET::ERR_CERT_COMMON_NAME_INVALID > > cert is internal CA and the sigature algorithim is Sha512RSA hash is SHa512 > > The only thing that looks a little questionable is in the subject, I also > have the serial number and the hostname is CAPs not lower case > > UCCx 11.5.1.10000-61 > > > Any thoughts? > > TIA > > Scott > >
_______________________________________________ cisco-voip mailing list cisco-voip@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-voip
