DV certificate orders: Domain validation scope settings for DCV emails
We improved the DCV email validation process for DV certificate orders, allowing you to set the domain validation scope when resending the DCV emails.
Note: Previously, when using the DCV email method to validate subdomains on your DV order, you had to validate the exact subdomain name.
Now, on your DV certificate order, you can validate a subdomain ( sub.example.com) at a higher level (example.com) by resending the DCV email to a higher-level domain email address (admin@example.com).
To learn more about the Email DCV method:
CertCentral Services API: Improved DV SSL: Resend emails endpoint
In the DigiCert Services API, we updated the DV SSL: Resend emails endpoint, enabling you to set the domain validation scope when resending the DCV emails for your DV certificate orders. We added a new optional parameter, "email_domain": "{{domain}}", that allows you to specify the domain where the email entry can be found by WHOIS.
Note: Previously, when using the DCV email method to validate subdomains on your DV order, you had to validate the exact subdomain name.
Now, on your DV certificate order, you can validate a subdomain (e.g., sub.example.com) at a higher level (e.g., example.com). Add the new parameter, "email_domain": "{{domain}}", to the resend DCV email request and send the DCV email to a higher-level domain email address (e.g., admin@example.com).
Example request for the DV SSL: Resend emails endpoint
CertCentral 服务 API:改进的“提交以进行验证”端点
在 DigiCert 服务 API 中,我们更新了提交以进行验证端点,让您可以在验证到期前提交域进行重新验证。现在,您可以随时提交域进行重新验证,让您可以提前完成域验证,对域保持无缝衔接的证书颁发流程。
注意:如果在域重新验证处于待处理状态时为域订购证书,我们会使用域的当前验证颁发证书。
新请求参数:dcv_method
我们还新增了请求参数,dcv_method*。现在,当您提交域进行验证时,可以更改证明对域的控制权时所使用的 DCV 方法。
*注意:该新参数可选。如果您在请求中删除新参数,我们会返回无内容的 204 响应。您需要使用之前在证明对域的控制权时所使用的相同 DCV 方法。
具有新参数的请求示例
POST https://www.digicert.com/services/v2/domain/{{domain_id}}/validation
请求中包含新参数时的响应示例
201 Created
CertCentral 服务 API:改进的订单文档签名 - 组织 (2000) 和 (5000) 端点:
在 DigiCert 服务 API 中,我们更新了用于订购文档签名 - 组织 (2000) 和 (5000) 证书的订购文档签名证书。我们新增了参数,"use_org_as_common_name": true
,,让您可以使用组织名称作为证书上的公用名。
注意:以前,您的唯一选项是使用个人的全名作为文档签名组织证书上的公用名。
现在,如果您要使用组织名称作为文档签名组织证书上的公用名,则在证书请求中添加 "use_org_as_common_name": true
参数。当我们颁发证书时,该组织名称将成为证书上的公用名。
文档签名证书订购端点示例