Using Single Subject Alternative Name Certificates

A newly supported scenario in Lync Server is the capability to use a single certificate that contains many subject alternative names. This certificate can then be exported and used on both Edge Servers and reverse proxy servers. Although this simplifies the number of certificates required, it might not actually be any less expensive than using a few single name certificates. This may vary depending on the number of SIP domains and simple URLs configured. The advantage to this approach is names for the simple URLs for meetings or dial-in conferencing can be added to the same certificate and used on the reverse proxy server.

Following is an example of what a certificate like this looks like that would then be placed on each Edge Server and reverse proxy server. Each Edge Server still requires a separate, internally issued certificate for the internal-facing interface. In this scenario, a single subject alternative name certificate can be placed on all Edge Servers and reverse proxy servers.

Subject name: sip.companyabc.com

Subject alternative names: sip.companyabc.com, webconf.companyabc.com, av.companyabc.com, lyncpoolweb.companyabc.com, dialin.companyabc.com, and meet.companyabc.com