大网数据广告活动
服务器运维问答

Subject Alternative Names required in a SAN CSR?

· 52CE 我爱测

We want to use a SAN SSL certificate for the following domains: example.com (common name) abc.example.com def.example.com www.abc.example.com www.def.example.com When creating the CSR for this certificate, do I have to enter all …

问题原文

原帖链接 · Zeep · CC BY-SA 4.0

We want to use a SAN SSL certificate for the following domains:

  • example.com (common name)
  • abc.example.com
  • def.example.com
  • www.abc.example.com
  • www.def.example.com

When creating the CSR for this certificate, do I have to enter all these hostnames (beside the Common Name) into the Subject Alternative Names section? Is it required? Or can I leave them empty and only fill out the Common Name?

How do these SAN entries eventually get into the SSL certificate? Is this through the CSR (if they've been provided) or can a certificate provider add them during the generation process, and thus the SANs are not required in the CSR?

已采纳解答

原帖链接 · Sam Erde · CC BY-SA 4.0

Yes, you need to include each of the subject alternate names and the subject/common name in the Subject Alternate Names section of the CSR. Some certificate authorities will allow you to update a certificate to add new SANs to it, but this always requires an updated CSR.

DigiCert is a fantastic CA to use, and here are their instructions for adding a SAN to a certificate.

To add SANs to a certificate, you must generate a new CSR on your server, and then submit the CSR in your account. If you need instructions for creating the CSR, see our Create a CSR (Certificate Signing Request) page.

The full instructions are here: https://www.digicert.com/multi-domain-add-subject-alternative-names.htm.

How you create your initial CSR will vary depending on what platform you are creating and using the certificate on.

摘自公开归档,保留原文语言,版式经整理,外部媒体与邮箱地址已移除。

资料来源与适用范围

资料来源
Server Fault
适用范围
以原帖系统、软件版本与发布日期为准(2018-06-06)
内容语言
中文;命令、路径和错误标识保留技术原文
本地收录日期
2026-11-15
授权说明
CC BY-SA 4.0

正文与所需资源由本站本地存储。查看来源及更新记录 ↗

请按适用版本和实际日志确认原因;本站没有对每一种系统或设备逐项执行文中的操作。