[cisco-voip] CUCM / Unity 10.5 and Tomcat SAN SSL

[Anthony Holloway]

I have successfully removed the -ms for COMODO as they didn't like it
either.  So, go for it.

I tried a quick search on the web t confirm my thoughts that the names are
not case-sensitive, but I was only finding a few opinions on the matter,
and the official RFC doesn't help much either.
http://tools.ietf.org/html/rfc5280#section-4.2.1.6

I'm going going to stick with, no, the case does not matter.  However, I
personally would always do everything all lower case if I had it my way.

On Fri, Sep 11, 2015 at 12:50 PM Michael David <mdavid at sps186.org> wrote:

> Greetings,
>
> When I generate the SAN CSRs, the server sets the common name to, for
> example, VUNITY1.sps186.org-ms - the "-ms" being added automatically to
> the end.  All the SANs in the list correspond to the actual hostnames and
> domain name. Can I change this CN to remove the -ms?  GoDaddy isn't
> allowing the cert to be created because the CN isn't a FQDN.  Not sure if
> the CUCM/Unity stuff needs the -ms for its own uses.
>
> Furthermore, our vendor set the hostnames to, for exmple, VUNITY1, VUCM1,
> etc rather than vunity1, vucm1.  GoDaddy changed the case from CSRs from
> the uppercase format to the lowercase format.  If the certs generate with
> the lowercase-only names, will they still function on the cluster with the
> cluster hostnames uppercase?
>
> Thanks in advance,
> Michael
>
> --
> Michael A. David, CCNA
> Springfield Public Schools
> Technology Service Center
> 217.585.5802 ext. 85114
> 217.585.5809 (FAX)
>
> _______________________________________________
> cisco-voip mailing list
> cisco-voip at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20150911/ff7c840d/attachment.html>