篩選依據: api x 清除
new

Upcoming Emergency Maintenance

On Sunday June 28, 2020 from 07:00 to 08:00 UTC DigiCert will perform emergency maintenance.

How does this affect me?

During this time, DigiCert will be unable to issue certificates for DigiCert platforms and their corresponding APIs, legacy Symantec consoles and their corresponding APIs, for immediate certificate issuance, and for those using the APIs for automated tasks.

Emergency maintenance affects:

  • CertCentral / Service API
  • Certificate Issuing Service (CIS)
  • Complete Website Security (CWS) / API
  • Direct Cert Portal / API
  • Managed PKI for SSL (MSSL) / API

Services will be restored as soon as maintenance is completed.

What can you do?

Please plan accordingly. Schedule high-priority orders, renewals, reissues, and duplicate issues outside of the maintenance window.

If you use the API for automated tasks, expect interruptions during this time.

enhancement

Legacy account upgrades to CertCentral: Mark migrated certificate orders as renewed

When you migrate a certificate order from your legacy console and then renew it in CertCentral, the original order may not get updated automatically to reflect the renewal. To make it easier to manage these migrated certificates, we added a new option—Mark renewed.

The Mark renewed option allows you to change the certificate order's status to Renewed. In addition, the original migrated certificate no longer appears in expiring or expired certificate lists, in the expiring or expired certificate banners, or on the Expired Certificates page in CertCentral.

Mark a migrated order as renewed

In CertCentral, in the left main menu, go to Certificates > Orders. On the Orders page, in the certificate order's Expires column, click Mark renewed.

Renewed filter

To make it easier to see the migrated certificate orders that have been marked renewed, we added a new filter—Renewed. On the Orders page, in the Status filter dropdown, select Renewed and click Go.

To learn more, see Mark a migrated certificate order as renewed.

enhancement

Legacy API upgrades to CertCentral Services API: Update order status endpoint improvements

When you migrate an order from your legacy console and then renew it in CertCentral, the original order may not get updated automatically to reflect the renewal.

To prevent these "renewed" orders from appearing alongside orders that still need to be renewed, we added a new value—renewed—to the status parameter on the Update order status endpoint.

Now, when you know a migrated certificate order has been renewed, you can manually change the status of the original order to renewed.

Example request with new status parameter

Update order status-endpoint example-request

To learn more, see Update order status.

new

New addition to DigiCert Developers portal

We are happy to announce a new addition to the DigiCert Developers portal—CT log monitoring API. For DigiCert API integrations, use these endpoints to manage the CT log monitoring service that is included with your Secure Site Pro certificate order. See CT log monitoring API.

CT Log Monitoring services

CT log monitoring allows you to monitor the public CT logs for SSL/TLS certificates issued for the domains on your Secure Site Pro certificate order, in near real time.

CT log monitoring is a cloud service so there is nothing to install or manage. After we've issued your Secure Site Pro, and you've turned CT Log monitoring for the order, you can start using the service immediately to monitor the domains on the Secure Site Pro certificate order.

enhancement

CertCentral Services API: Improved order endpoints:

In the DigiCert Services API, we added a "domain ID" response parameter to the endpoints listed below. Now, when you add domains--new or existing--in your certificate request, we return the domain IDs in the response.

This reduces the number of API calls needed to get the domain IDs for the domains on the certificate order. It also allows you to perform domain-related task immediately, such as change the DCV method for one of the domains on the order or resend the WHOIS emails.

Note: Previously, after adding new or existing domains in your certificate request, you had to make an additional call to get the domain IDs: List domains or Domain info.

Updated order endpoints

Example response with new domain ID parameter

Order endpoints' example reponse with new domains parameter

enhancement

CertCentral Services API: Improved Revoke order certificates and Revoke certificate endpoints

In the DigiCert Services API, we updated the Revoke order certificates and Revoke certificate endpoints, enabling you to skip the approval step when revoking a certificate.

Note: Previously, the approval step was required and could not be skipped.

We added a new optional parameter, "skip_approval": true, that allows you to skip the approval step when submitting a request to revoke one certificate or all certificates on an order.

Note: For skip approvals to work for certificate revoke requests, the API key must have admin privileges. See Authentication.

Now, on your revoke certificate and revoke order certificate requests, you can skip the approval step and immediately submit the request to DigiCert for certificate revocation.

Example request for the revoke certificate and revoke order certificates endpoints

Example revoke certificate request with skip_approval parameter

fix

Bug fix: DV certificate issuance emails did not respect certificate format settings

We fixed a bug in the DV certificate issuance process where the Your certificate for your-domain email notification did not deliver the certificate in the format specified in your account settings.

Note: Previously, we included a certificate download link in all DV certificate issued email notifications.

Now, when we issue your DV certificate order, the email delivers the certificate in the format specified in your account's Certificate Format settings.

Configure certificate format for certificate issuance emails

In the left main menu, go to Settings > Preferences. On the Division Preferences page, expand Advance Settings. In the Certificate Format section, select the certificate format: attachment, plain text, or download link. Click Save Settings.

enhancement

Updates to the Domain details page

We simplified the Domain Validation section on the Domain details page to display only two validation types with their expiration dates: OV and EV. We also updated the page to show the domain validation expiration dates calculated from when the Domain Control Verification (DCV) was completed (OV: +825 days, EV: +13 months).

Note: Previously, you could see up to two other validation types: Grid and Private. Grid certificates have the same validity period as OV: 825 days. Domain validation is not required for private certificates as these certificates are not publicly trusted.

To view a domain's validation expiration dates, in the left main menu, go to Certificates > Domains. On the Domains page, locate the domain and click its Domain Name link. On the Domain details page, under Domain Validation, view your domain validations and when they expire.

enhancement

CertCentral Services API: Improved List domains and Domain info endpoints

In the DigiCert Services API, we updated the List domains and Domain info endpoints, enabling you to see when the domain control validations (DCV) for the domain expire: OV and EV validations. This new information is only returned in the response if you include the URL query string include_validation=true.

Now, when you get a list of all domains or information about a specific domain and you include the URL query string include_validation=true, you can see when the DCVs for the domain expire.

Example requests with the URL query string:

  • Domain info
    https://www.digicert.com/services/v2/domain/{{domain_id}}? include_validation=true
  • List domains
    https://www.digicert.com/services/v2/domain?include_validation=true

Example response – domain control validation (DCV) expiration dates

Example response with DCV expiration dates

fix

Removed "Pending" column from Domains page

We found a bug on the Domains page preventing us from providing accurate information about a domain's pending validations. As a temporary solution, we are removing the Pending column from the page until a permanent fix can be deployed.

To view if a domain has pending validations, in the left main menu, go to Certificates > Domains. On the Domains page, locate the domain and click its Domain Name link. On the Domain details page, under Domain Validation, check to see if the domain has pending validations: OV and EV.

二月 28, 2020

enhancement

CertCentral Services API: Improved rate limits

In the DigiCert Services API, we improved our requests rate limits. Now, we enforce a rate limit of 1000 requests per 5 minutes, along with a short-term rate limit of 100 requests per 5 seconds to protect against burst requests and prevent abuse*.

*Note: If the number of requests exceeds either rate limit, API access is temporarily blocked, and all requests return a 429 HTTP status code (request_limit_exceeded) with a "Service unavailable, please limit request volume" message.

For more information, see Rate limits.

fix

We fixed a bug in CertCentral where "hidden" organizations prevented certificate request forms from opening. To fix this issue, we no longer include hidden organizations in the list of available organizations on the certificate request forms.

What if I want to add a "hidden" organization to a certificate request?

To include a "hidden" organization in the list of available organizations on your certificate request forms, simply unhide it.

  1. In the left main menu, go to Certificates > Organizations.
  2. On the Organizations page, in the Hidden Organizations dropdown, select Show and then click Go.
  3. Click the organization, you want to unhide.
  4. On the Organization's detail page, click Unhide.

The next time you order a certificate, the organization will appear in the list of available organizations on the certificate request form.

Note: This change only affects the CertCentral user interface (UI). The API supports adding "hidden" organizations to your requests; you don’t need to unhide an organization to add it to a certificate request.

new

Legacy account upgrades to CertCentral

In the DigiCert Service API, we added a new endpoint—DigiCert order ID—to make it easier to find the corresponding DigiCert order IDs for your migrated legacy Symantec orders.

After you migrate your active, public SSL/TLS certificate orders to your new account, we assign a unique DigiCert order ID to each migrated legacy Symantec SSL/TLS certificate order.

Example request

GET https://www.digicert.com/services/v2/oem-migration/{{symc_order_id}}/order-id

Example response
200 OK

Example response for Digicert order ID endpoint

For more information:

new

In the DigiCert Services API, we added four new endpoints for ordering the new more flexible Basic and Secure Site SSL/TLS certificates. These more flexible SSL/TLS certificates make it easier to get the certificate to fit your needs and will replace the old Basic and Secure Site products.

Use these endpoints to place new orders and renewal orders only. They cannot be used to convert existing Basic or Secure Site certificate orders.

To activate any of these new certificates for your CertCentral account, contact your account manager or our Support team.

  • Order Basic OV
    POST https://www.digicert.com/services/v2/order/certificate/ssl_basic
  • Order Basic EV
    POST https://www.digicert.com/services/v2/order/certificate/ssl_ev_basic
  • Order Secure Site OV
    POST https://www.digicert.com/services/v2/order/certificate/ssl_securesite_flex
  • Order Secure Site EV
    POST https://www.digicert.com/services/v2/order/certificate/ssl_ev_securesite_flex

Flexible OV and EV certificates

These certificates provide the encryption and authentication you've come to expect from DigiCert SSL/TLS certificates, while allowing you to build an OV or EV certificate with a mix of whatever domains and wildcard domains* are needed to fit your needs.

*Note: Industry standards support wildcard domains in OV SSL/TLS certificates only. EV SSL/TLS certificates don't support the use of wildcard domains.

fix

CertCentral Services API: Fixed Revoke certificate endpoint bug

In the DigiCert Services API, we fixed a bug in the Revoke certificate endpoint where the request to revoke a single certificate on an order was being submitted for all certificates on the order.

Note: After submitting your "single certificate" revocation request, we returned a 201 Created response with the request details to revoke all certificates on the order.

Now, when using the Revoke certificate endpoint to submit a request to revoke a single certificate on an order, we return a 201 Created response with the request details to revoke just that certificate on the order.

30-day money back guarantee

The Revoke certificate endpoint revokes a certificate on the order and not the order itself. Our 30-day money back guarantee is tied to an order and not a "certificate" on the order. To get the 30-day money back guarantee, you need to revoke the order within the first 30 days; see Revoke order certificates.

Certificate revocation process

All revocation requests, including those made via the Services API, must be approved by an administrator before DigiCert will revoke the certificate. This approval step is required and cannot be skipped or removed from the certificate revocation process.

*What you need to know about the revoke certificate endpoint

This endpoint is designed to revoke a certificate on an order; it doesn't revoke a certificate order.

If you revoke a certificate on an order with only a single certificate:

  • The order is still active
  • No refund is provided for the revoked certificate
  • You can still reissue a certificate on that order

If you don't plan to reissue a certificate for the order, use the Revoke order certificates endpoint to revoke the order.

enhancement

CertCentral Services API: Improved Submit for validation endpoint

In the DigiCert Services API, we updated the Submit for validation endpoint, enabling you to submit a domain for revalidation before it expires. Now, you can submit a domain for revalidation at any time, enabling you to complete the domain’s validation early and maintain seamless certificate issuance for the domain.

Note: If you order a certificate for the domain while the domain's revalidation is in a pending state, we use the domain's current validation to issue the certificate.

New request parameter: dcv_method

We also added a new request parameter, dcv_method*. Now, when you submit a domain for validation, you can change the DCV method used to prove control over the domain.

*Note: This new parameter is optional. If you leave the new parameter out of your request, we return a 204 response with no content. You will need to use the same DCV method used before to prove control over the domain.

Example request with new parameter
POST https://www.digicert.com/services/v2/domain/{{domain_id}}/validation

Submit for validation endpoint example request

Example response when new parameter is included in the request
201 Created

Submit for validation endpoint example response

一月 14, 2020

enhancement

CertCentral Services API: Improved order endpoints:

In the DigiCert Services API, we added an "organization ID" response parameter to the endpoints listed below. Now, when you add a new organization in your certificate request, we return the organization's ID in the response, enabling you to use the organization immediately in your certificate requests.

Previously, after adding a new organization in your certificate request, you had to make an additional call to get the new organization's organization ID: Order info.

Updated order endpoints:

Example response with new organization ID parameter

Example response with new organization ID parameter

enhancement

11 SUPPORTED LANGUAGES IN THE DOC AND DEVELOPERS PORTALS

As we work to globalize our product offerings and make our websites, platforms, and documentation more accessible, we are happy to announce that we've added language support to the Document and Developers portals.

We now support these 11 languages:

  • English
  • Chinese (Simplified)
  • Chinese (Traditional)
  • French
  • German
  • Italian
  • Japanese
  • Korean
  • Portuguese
  • Russian
  • Spanish

How does language support work?

When you visit the portals, use the language selector (globe icon) to change the portal display language. We save your language selection for 30 days so you don't need to reselect it every time you visit our documentation site.

TIPS AND TRICKS

Access Doc and Developer portals

You can access the Document and Developers portals from the DigiCert website and CertCentral.

  • From digicert.com
    In the top menu, hover over Support. Under Resources, you can find Documentation and API Documentation links.
  • From CertCentral
    In the Help menu, select Getting Started.
    On the API Keys page, click API Documentation. (In the left main menu, go to Automation > API Keys).

Create links within documentation

You can link to sections within the documentation.

On the documentation page, hover on the subheader you want to link to and click the hashtag icon (#). This creates a URL in the browser's address bar.

Use this feature to bookmark or link to specific sections in the instructions.

enhancement

CertCentral Services API: Improved order Document Signing - Organization (2000) and (5000) endpoints:

In the DigiCert Services API, we updated the Order document signing certificate endpoints for ordering Document Signing - Organization (2000) and (5000) certificates. We added a new parameter, "use_org_as_common_name": true, enabling you to use the organization name as the common name on the certificate.

Note: Previously, your only option was to use the person's full name as the common name on your document signing organization certificates.

Now, if you want to use the organization name as the common name on your document signing organization certificate, add the "use_org_as_common_name": true parameter to your certificate request. When we issue your certificate, the organization name will be the common name on the certificate.

  • Document Signing - Organization (2000) endpoint: https://www.digicert.com/services/v2/order/certificate/document_signing_org_1
  • Document Signing - Organization (5000) endpoint: https://www.digicert.com/services/v2/order/certificate/document_signing_org_2

Example request for Order document signing certificate endpoint

Example Document Signing Organization certificate request

enhancement

Improved client certificate process

We improved the client certificate process, enabling you to cancel client certificate orders in an Emailed to Recipient state—orders that are waiting for the email recipient to generate and install the client certificate in one of the supported browsers.

Note: Previously, when a client certificate was in an Emailed to Recipient state, you had to contact support to cancel the order.

Now, if you need to cancel a client certificate order in the Emailed to Recipient state, go to the client certificate's Order details page and in the Certificate Actions dropdown list, select Cancel Order. See Cancel pending client certificate orders.

enhancement

CertCentral Services API: Improved client certificate process
In the DigiCert Services API, we updated the Update order status endpoint enabling you to cancel client certificate orders in a waiting_pickup state—orders that are waiting for the email recipient to generate and install the client certificate in one of the supported browsers.

Note: Previously, when a client certificate was in a waiting_pickup state, you received a forbidden error and had to contact support to cancel the order.

Now, you can use the Update order status endpoint to cancel a client certificate order in the waiting_pickup state.

new

In the DigiCert Services API, we added a new endpoint – Additional emails. This endpoint allows you to update the email addresses that receive certificate notification emails for the order (e.g., certificate renewals, reissues, and duplicate orders).

Note: These people can't manage the order. They only receive certificate related emails.

For more information on the Services API, see our Developers portal.

十一月 8, 2019

new

We are happy to announce a new addition to the DigiCert Developers portal—Discovery API. We just published our first set of Discovery API endpoints. More will follow as we continue to build out the Discovery API documentation.

Why use it?

  • Access Discovery features without signing into your CertCentral account.
  • Customize the Discovery experience to meet the needs of your organization.
  • Integrate with your existing tools.

Sample of endpoints you can start using now:

Tips and Tricks

  • Discovery API uses this base URL: https://daas.digicert.com/apicontroller/v1/
  • Discovery API requires admin or manager level permissions.
new

In our CertCentral API, we added a new Custom Reports API that leverages the powerful GraphQL query language, enabling you to generate comprehensive and customizable data sets for more robust reporting.

Custom Reports API consolidates multiple REST endpoints into a single one, so you can better define the types and fields in your queries so they return only the information needed. Additionally, use it to create reusable query templates for generating and scheduling reports.

To learn more, see Custom Reports API in our Developers portal.

new

We added two new features to the Expiring Certificates page (in the sidebar, click Certificates > Expiring Certificates), making it easier to manage renewal notifications for your expiring certificates.

First, we added a Renewal Notices column with an interactive check box. Use this check box to enable or disable renewal notices for an expiring certificate.

Second, we added two Renewal Notices filters: Disabled and Enabled. These filters allow you to see only the certificate orders with renewal notices enabled or disabled.

enhancement

In the DigiCert Services API, we updated the List keys and Get key info endpoints response parameters, enabling you to see the organization associated with your ACME certificate orders.

Now, when you call the List keys and Get key info endpoints, we return the name of the organization (organization_name) associated with the ACME certificate order in the response.

Get key info: example reponse with new parameter

new

In the DigiCert Services API, we added two new Order info endpoints. Now, you can use the order ID, the certificate's serial number, or the certificate's thumbprint to view the details for a certificate order.

  • GET https://www.digicert.com/services/v2/order/certificate/{{thumbprint}}
  • GET https://www.digicert.com/services/v2/order/certificate/{{serial_number}}

Currently, these new endpoints only retrieve data for the primary certificate. For more information on the Services API, see our Developers portal.

new

PQC dockerized toolkit guide available now

Secure Site Pro Secure Site Pro certificates come with access to the DigiCert post-quantum cryptographic (PQC) toolkit. To create your own PQC test environment, use one of these options:

Our toolkits contain what you need to create a hybrid SSL/TLS certificate. The hybrid certificate in the toolkits uses a PQC algorithm paired with an ECC algorithm allowing you to test the feasibility of hosting a post-quantum, backwards compatible hybrid certificate on your website.

Note: To access your PQC toolkit, go to your Secure Site Pro Certificate's Order # details page. (In the sidebar menu, click Certificates > Orders. On the Orders page, click the order number link for your Secure Site Pro certificate. On the certificate's order details page, click PQC toolkit.)

To learn more about post-quantum cryptography, see Post-Quantum Cryptography. To learn more about what's included with each Secure Site Pro certificate, see Pro TLS/SSL Certificates.

new

DigiCert is happy to announce we made it easier for DigiCert Accounts using the Retail API to upgrade to our new Certificate Management Platform, DigiCert CertCentralFor free!

To make the upgrade as seamless as possible, we shimmed these Retail API endpoints:

Now, you can upgrade your DigiCert Account without any interruptions to your API integrations. Once you're upgraded, make plans to build new integrations with CertCentral.

  • For more information on the CertCentral Services API, see our Developers portal.

For information about the DigiCert Retail API, see Documentation for the DigiCert Retail API.

enhancement

In Discovery, we updated the Certificates page, adding a new action—Replace certificate—to the Actions dropdown. Now, from the Certificates page, you can replace any certificate with a DigiCert certificate regardless of issuing CA.

(In the sidebar menu, click Discovery > View Results. On the Certificates page, locate the Actions dropdown for the certificate you want to replace. Click Actions > Replace certificate.)

enhancement

In Discovery, we updated the Certificates by rating widget on the Discovery dashboard, making it easier to see the security ratings for your public SSL/TLS certificates (in the sidebar menu, click Discovery > Discovery Dashboard).

As part of the update, we renamed the widget: Certificates analyzed by security rating. Then, we split the chart on the widget into two charts: Public and Others. Now, you can use the Public | Others toggle switch on the widget to select the chart you want to see.

The Certificates analyzed by security rating - Public chart displays the ratings for your public SSL/TLS certificates only. The Certificates analyzed by security rating - Other chart displays the rating for all your other SSL/TLS certificates (e.g., private SSL certificates).

enhancement

In Discovery, we updated the Endpoints and Server details pages making it easier to see the correlation between the IP address and the hostname/FQDN scan it resulted from.

Now, when you configure a scan for a hostname/FQDN, and the scan's endpoint results return IP addresses, we include the hostname/FQDN from the scan with the IP address.

Update note: The hostname update is available in the latest sensor version – 3.7.10. After the sensors updates are completed, rerun scans to see the hostname/IP address correlation on your scan results.

new

In the DigiCert Services API, we added two new endpoints for ordering your Secure Site Pro certificates: Order Secure Site Pro SSL and Order Secure Site Pro EV SSL.

  • POST https://www.digicert.com/services/v2/order/certificate/ssl_securesite_pro
  • POST https://www.digicert.com/services/v2/order/certificate/ssl_ev_securesite_pro

Benefits included with each Secure Site Pro certificate

Each Secure Site Pro certificate includes – at no extra cost – first access to premium feature such as the Post Quantum Cryptographic (PQC) toolkit.

Other benefits include:

  • Priority validation
  • Priority support
  • Two premium site seals
  • Malware check
  • Industry-leading warranties – protection for you and your customer!

To learn more about our Secure Site Pro certificates, see DigiCert Secure Site Pro.

To activate Secure Site Pro certificates for your CertCentral account, contact your account manager or our support team.

enhancement

在 DigiCert Service API 中,我們更新了列出重新發行端點回應參數,讓您可以看到收據 ID、購買的網域數目、重新發行的訂單上購買的萬用字元網域數目。

現在,我們將在您的重新發行的憑證的訂單詳細資料中,傳回可用的這些回應參數:

  • receipt_id
  • purchased_dns_names
  • purchased_wildcard_names
Example of the new List reissues endpoint response-parameters

enhancement

我們改良了「訂單的重新發行憑」頁面上的交易摘要,允許您查看到憑證到期剩下多少天。現在,當您重新發行憑證時,交易摘要會顯示憑證有效期限與直到到期的天數 (例如 1 年 (在 43 天到期)。

enhancement

在 DigiCert Services API 中,我們更新了列出訂單,訂單資料,列出重新發行,和列出複本端點,讓您可以查看到憑證到期剩下多少天。關於些端點,我們在其回應中傳回 days_remaining 參數。

Example of the days_remaining response parameter.png

enhancement

我們改良了與 CertCentral 整合的 SAML 單一登入 (SSO) 的使用者邀請工作流程,讓您可以在傳送您的帳戶使用者邀請前,指定受邀者為僅限 SSO 使用者。現在,在邀請新使用者彈出視窗中,使用僅 SAML 單一登入 (SSO) 選項限制到僅 SAML SSO 的受邀者。

註:此選項停用這使用者的所有其他驗證方法。此外,此選項僅在您已對您的 CertCentral 帳戶啟用 SAML 時出現。

(在資訊看板功能表中,按一下帳戶 > 使用者邀請。在「使用者邀請」頁面上,按一下邀請新使用者。請參閱 SAML SSO:邀請使用者加入您的帳戶。)

簡化的註冊表

我們也簡化了僅 SSO 使用者註冊表,移除密碼和安全問題要求。現在,僅 SSO 受邀者需要只新增他們的個人資料。

new

我們讓從您帳戶中的 CertCentral 儀表板查看您的「探索」憑證掃描結果變得更加容易,新增探索即將到期的憑證、,憑證發行者,和依等級分析的憑證小工具。

每個小工具都包含一個互動圖表,允許您深入研究以輕鬆尋找更多與即將到期的憑證 (例如哪一份憑證將在 8 到 15 內到期)、依發行 CA (例如 DigiCert) 的憑證和依安全評價的憑證 (例如不安全) 有關的資訊。

更多有關探索的資訊

「探索」使用感應器掃描您的網路。從您的 CertCentral 帳戶內部,集中設定和管理掃描。

new

在 DigiCert Services API 中,我們更新了訂單資訊端點,讓您可以查看如何要求憑證。關於透過 Services API 或 ACME Directory URL 要求的憑證,我們會傳回一個新的回應參數:api_key. 此參數包括金鑰名稱與金鑰類型:API 或 ACME。

註:關於透過其他方法 (例如 CertCentral 帳戶、訪客要求 URL 等) 要求的訂單,從回應中省略 api_key 參數。

現在,在檢視訂單詳細資料時,您將會看到用於透過 API 或 ACME Directory URL 要求的訂單的回應中的新 api_key 參數。

取得 https://dev.digicert.com/services-api/order/certificate/{order_id}

回應:

Order info endpoint response parameter

new

我們新增了新的搜尋篩選器 – 要求方式 – 透過「訂單」頁面,允許您搜尋透過特定的 API 金鑰或 ACME Directory URL 要求的憑證訂單。

現在,在「訂單」頁面上,使用要求方式篩選器,透過特定的 API 金鑰或 ACME Directory URL 要求尋找要求的啟用、到期、已撤銷、已拒絕、擱置的重新發行、擱置的和重複的憑證。

(在資訊看板功能表中,按一下憑證 > 訂單。在「訂單」頁面上,按一下顯示進階搜尋。然後在要求方式下拉清單中,選擇 API 金鑰或 ACME Directory URL 名稱,或在方塊中輸入其名稱。)

enhancement

我們改良我們的 Basic 和 Secure Site 單一網域憑證方案 (Standard SSL、EV SSL、Secure Site SSL 和 Secure Site EV SSL),新增在憑證中納入[your-domain].com 和 www.[your-domain].com 選項到這些憑證的訂單中、重新發行和重複的表格。此選項允許您選擇是否在這些單一網域憑證中,免費納入兩個版本的一般名稱 (FQDN)。

  • 若要保護兩個版本的一般名稱 (FQDN) 的安全,請勾選在憑證中納入[your-domain].com 和 www.[your-domain].com
  • 若只要保護一般名稱 (FQDN) 的安全,請取消勾選在憑證中納入[your-domain].com 和 www.[your-domain].com

請參閱訂購您的 SSL/TLS 憑證

也適用於子網域

新選項允許您取得兩個版本的基礎和子網域。現在,若要保護兩個版本的子網域的安全,請新增子網域到一般名稱方塊中 (sub.domain.com),然後勾選在憑證中納入[your-domain].com 和 www.[your-domain].com。當 DigiCert 發行您的憑證時,將納入憑證上兩個版本的子網域:[sub.domain].com 和 www.[sub.doman].com。

移除子網域的使用附加功能

在憑證中納入[your-domain].com 和 www.[your-domain].com 選項,使附加功能 -- 使用子網域的附加功能過時。因此,我們從「分區喜好設定」頁面移除選項 (在資訊看板功能表中,按一下設定 > 喜好設定)。

enhancement

在 DigiCert Services API 中,我們更新了 Order OV/EV SSL,Order SSL (type_hint),Order Secure Site SSL,Order Private SSL,Reissue 憑證,和以下所列的重複的憑證端點。這些變更在要求、重新發行和複製您的單一網域憑證時提供更多控制權,允許您選擇是否在這些單一網域憑證上,免費納入特定的其他 SAN。

  • /ssl_plus
  • /ssl_ev_plus
  • /ssl_securesite
  • /ssl_ev_securesite
  • /private_ssl_plus
  • /ssl*
  • /reissue
  • /duplicate

*註:關於 Order SSL (type_hint) 端點,僅限使用如下述的 dns_names[] 參數來新增免費的 SAN。

保護您的兩個版本的網域的安全 ([your-domain].com 和 www.[your-domain].com),在您的要求中,使用 common_name 參數新增網域 ([your-domain].com) 和 dns_names[] 參數新增其他版本的網域 (www.[your-domain].com)。

當 DigiCert 發行您的憑證時,將保護您的兩個版本的網域的安全。

example SSL certificte request

若只要保護一般名稱 (FQDN) 的安全,只要從您的要求中省略 dns_names[] 參數。

enhancement

在 DigiCert Services API 中,我們改良了重複的憑證端點工作流程。現在,如果可以立刻發行重複的憑證,我們會在回應本文中傳回重複的憑證。

如需更多資訊,請參閱重複的憑證

enhancement

我們改良了 CertCentral 中的重複的憑證訂購程序。現在,如果可以立刻發行重複的憑證,我們會將您直接引導到複本頁面,在此您可以立刻下載憑證。

四月 16, 2019

enhancement

我們已更新 CertCentral 說明功能表中和「帳戶存取」頁面上的文件連結,以指向我們的新文件入口網站。

現在,在 CertCentral 說明功能表中,,當您按下開始使用時,,我們會將您引導到我們新的 DigiCert 文件入口網站。同樣的,當您按下變更記錄時,,我們會將您引導到我們改良的變更記錄頁面。現在,在帳戶存取頁面上 (在資訊看板功能表中,按一下帳戶 > 帳戶存取),當您按下 API 文件時,,我們會將您引導到我們新的 DigiCert 開發人員入口網站

四月 2, 2019

new

我們很樂意發佈新的 DigiCert 文件入口網站。新網站有充滿現代感的外觀和感覺,並且包含簡化的、基於任務的說明文件、產品新聞、變更記錄和 API 開發人員文件。

我們也很樂意宣佈新的 DigiCert 開發人員入口網站已脫離試用版的階段。新網站有充滿現代感的外觀和感覺,並且包含與可用的端點、使用情況和工作流程有關的資訊。

要訣與提示

  • 您可以存取在支援下 (按一下支援 > 文件) 的頂端功能表中的 www.digicert.com 的文件入口網站。
  • 在我們的文件中,將游標移到子標題上,然後按雜湊標記圖示。這將會在瀏覽器的位址列中建立 URL,因此您可以將指示中的特定區段加入書籤中或連結。

即將推出

開始使用包含協助您熟悉您帳戶中的功能的資訊。

三月 18, 2019

fix

在 DigiCert Services API 中,我們修復了訂單資訊端點中的漏洞,其中未傳回用於已發行的用戶端憑證訂單 (Authentication Plus、Email Security Plus 等) 的電子郵件地址。

註:在使用列出訂單端點擷取所有發行的憑證的資訊時,傳回用於用戶端憑證訂單的電子郵件地址。

現在,當您使用訂單資訊端點檢視已發行的用戶端憑證訂單的詳細資料時,以回應傳回電子郵件地址。

適用於 Authentication Plus 的訂單資訊回應的範例

fix

我們修復了組織單位 (OU) 項目字元限制漏洞,其中我們集體套用 64 位元限制,而非個別套用有多個 OU 的 SSL/TLS 憑證要求上的 OU 項目。當系統管理員嘗試要核准要求時,他們會錯誤的收到"必須小於 64 個字元的組織單位以符合業界標準"錯誤訊息。

註:此漏洞僅影響需要系統管理員核准的要求。

現在,當系統管理員核准有多個 OU 的 SSL/TLS 憑證要求時 (其中每個項目都在 64 個字元限制標準內),要求依預期提交給 DigiCert。

遵守注意事項:業界標準制訂了用於個別組織單位項目的 64 個字元限制。然而,當您新增多個 OU 到訂單時,每一個都會被個別計算,而且不會組合。請參閱公開受信任的憑證 – 違反業界標準的資料條目

fix

我們修復了憑證要求上的漏洞,其中您無法編輯被指派要求/憑證的分區。

註:一發行憑證後,您可以前往其訂單編號詳細資料頁面,以及編輯被指派憑證的分區。

山在,當您編輯憑證要求時,您可以變更被指派要求/憑證的分區。

三月 12, 2019

fix

我們修復了憑證重新發行漏洞,您可以在其中撤銷有擱置的重新發行的憑證。為了修復此漏洞,我們改良了重新發行憑證工作流程,從有擱置的重新發行的憑證上,移除撤銷憑證選項。

之前,當憑證有擱置的重新發行埘,您可以提交要求以撤銷原始的或之前發行的憑證。當系統管理員核准要求時,憑證會錯誤標示為正在要求頁面上遭到撤銷。然而在您前往訂單頁面時,憑證正確標記為已發行和仍然啟用中。

當憑證有擱置的重新發行時,您無法撤銷憑證,因為憑證已繫結憑證重新發行程序。如果在您需要撤銷有擱置的重新發行的憑證時,您有兩個選擇:

  1. 取消憑證重新發行,然後撤銷原始的或之前發行的憑證。
  2. 等待 DigiCert 重新發行憑證,然後撤銷憑證。
fix

我們修復了 DigiCert Services API 憑證重新發行漏洞,您可以在其中提交要求以撤銷有擱置的重新發行的憑證。當您使用撤銷憑證端點時,我們傳回有要求詳細資料的 201 Created 回應。

現在,當您使用撤銷憑證端點撤銷有擱置的重新發行的憑證時,我們以訊息傳回錯誤,讓您知道您無法撤銷有擱置的重新發行的訂單,以及您需要撤銷憑證時要如何進行的資訊。

"擱置重新發行時無法撤銷訂單。您可以取消重新發行,然後撤銷憑證,或一完成重新發行後即撤銷憑證。"

fix

我們修復了 DV 憑證重新發行漏洞,其中我們未注意到原始訂單上的有效日期,因為憑證直到到期剩下超過一年的時間。

現在,當您重新發行離到期還剩一年以上的 DV 憑證時,重新發行的憑證將保留原始憑證的截止有效日期。

enhancement

在 DigiCert Services API 中,我們改善了 DV 憑證要求端點,允許您使用新的 email_domain 欄位連同現有的 email 欄位,更準確的設定想要的網域控制驗證 (DCV) 電子郵件的收件人。

例如,在訂購用於 my.example.com 的憑證時,您可以請基礎網域 (example.com) 的網域擁有者驗證子網域。若要變更 DCV 電子郵件的電子郵件收件人,請在您的 DV 憑證要求中,新增 dcv_emails 參數。然後,新增指定基礎網域 (example.com) 的 email_domain 欄位,以及指定想要的 DCV 電子郵件收件人的電子郵件地址 (admin@example.com) 的 email 欄位。

要求 GeoTrust Standard DV 憑證的範例

DV 憑證端點:

enhancement

我們增強了 DigiCert Services API 要求端點,讓您可以取得對您的憑證要求的更快速回應。

enhancement

我們使用於 OV 憑證訂單 (Standard SSL、Secure Site SSL 等) 的新增聯絡人變得更容易。現在當您訂購 OV 憑證時,我們會為您填入組織聯絡人。需要時,您可以新增技術聯絡人。

  • 新增包含您帳戶中的現有組織的 CSR 時,我們會以指派給該組織的聯絡人填入組織聯絡人卡片中。
  • 手動新增現有的組織時,我們會以指派給該組織的聯絡人填入組織聯絡人卡片中。
  • 新增新組織時,我們會以您的聯絡人資料填入組織聯絡人卡片中。

若要使用不同的組織聯絡人,請刪除自動填入的一個,然後手動新增一個。

enhancement

我們使用於 EV 憑證訂單 (EV SSL、Secure Site EV SSL 等) 的新增聯絡人變得更容易。現在當您訂購 EV 憑證時,若您的帳戶有可用的 EV 已確認聯絡人資料,我們將為您填入已確認聯絡人卡片。需要時,您可以新增組織和技術聯絡人。

  • 新增包含您帳戶中的現有組織的 CSR 時,我們會以指派給該組織的 EV 已確認聯絡人填入已確認聯絡人卡片中。
  • 當您手動新增現有的組織時,我們會以指派給該組織的 EV 已確認聯絡人填入已確認聯絡人卡片中。

指派已確認聯絡人給組織不是新增組織的先決條件。有一些確認聯絡人資料不會用於組織的情況。在此情況中,請手動新增已確認聯絡人

二月 13, 2019

new

我們新增了兩個新端點,允許您使用 order_id 下載用於訂單的目前啟用的憑證。

這些端點僅可以用於取得用於訂單的最新重新發行憑證。這些端點無法用於下載重複的憑證。

重複的憑證注意事項

若要下載用於訂單的重複的憑證,首先請使用列出訂單複端點取得重複的憑證的 certificate_id – GET https://www.digicert.com/services/v2/order/certificate/{{order_id}}/duplicate

然後使用取得憑證端點下載重複的憑證 – GET https://www.digicert.com/services/v2/certificate/{{certificate_id}}/download/platform

重新發行憑證注意事項

若要下載過去重新發行的憑證 (不是目前重新發行的憑證),首先使用列出訂單重新發行端點,以取得重新發行憑證的 certificate_id -- GET https://www.digicert.com/services/v2/order/certificate/{{order_id}}/reissue

然後使用取得憑證端點下載重新發行的憑證 – GET https://www.digicert.com/services/v2/certificate/{{certificate_id}}/download/platform

API 文件注意事項

如需更多有關 DigiCert Services API 中的這些和其他可用端點的資訊,請參閱 CertCentral API

enhancement

我們增強了我們的 RapidSSL DV 憑證方案,讓您可以在這些單一網域憑證中,納入第二個非常特定的網域。

  • RapidSSL Standard DV
    現在根據預設值,在訂購 RapidSSL Standard DV 憑證時,您會得到憑證中兩個版本的一般名稱 —[your-domain].com 和 www.[your-domain].com。
    在輸入一般名稱後,確定勾選在憑證中納入 www.[your-domain].com 和[your-domain].com 方塊。
    之前,您必須分別訂購[your-domain].com 和 www.[your-domain].com 的憑證。
  • RapidSSL Wildcard DV
    現在根據預設值,在訂購 RapidSSL Wildcard DV 憑證時,您會得到憑證中的萬用字元網域和基礎網域 – *.[your-domain].com 和[your-domain].com。
    在輸入一般名稱後,確定勾選在憑證中納入 *.[your-domain].com 和[your-domain].com 方塊。
    之前,您必須分別訂購 *.[your-domain].com 和[your-domain].com 的憑證。

請參閱 CertCentral:DV 憑證註冊指南

enhancement

我們增強了 RapidSSL 憑證端點以納入 dns_names 參數,讓您可以在這些單一網域憑證中,納入第二個非常特定的網域。

  • RapidSSL Standard DV
    訂購 RapidSSL Standard DV 憑證時,您可在憑證中納入您的兩個版本的網域 — [your-domain].com 和 www.[your-domain].com。
    "common_name": "[your-domain].com",
    "dns_names":["www.[your-domain].com"],

    之前,您必須分別訂購[your-domain].com 和 www.[your-domain].com 的憑證。
  • RapidSSL Wildcard DV
    訂購 RapidSSL Wildcard DV 憑證時,您可在憑證中納入基礎網域 — *.[your-domain].com 和[your-domain].com)。
    "common_name": "*.your-domain.com",
    "dns_names":["[your-domain].com"],

    之前,您必須分別訂購 *.[your-domain].com 和[your-domain].com 的憑證。

關於 DigiCert Services API 文件,請參閱 CertCentral API

new

CertCentral 中提供可用的 Individual Document Signing 憑證:

  • Document Signing – Individual (500)
  • Document Signing – Individual (2000)

若要啟用使用於您的 CertCentral 帳戶的 Document Signing 憑證,請聯絡您的銷售代表。

之前,僅可以使用 Organization Document Signing (組織文件簽署) 憑證。

  • Document Signing – Organization (2000)
  • Document Signing – Organization (5000)

若要瞭解更多有關這些憑證的資訊,請參閱 Document Signing 憑證

enhancement

我們增強了我們的 SSL/TLS 和用戶端憑證產品方案,讓您可以在訂購這些憑證之一時,設定自訂的有效期限 (天數)。之前,您只能選擇自訂到期日。

自訂有效期間從我們發行憑證的那一天開始。憑證價格依比例分配以符合自訂的憑證時間長度。

註:自訂憑證長度不可超過業界允許的憑證最長生命周期期間。例如,您不可以將 SSL/TLS 憑證的有效期間設定為 900 天。

enhancement

我們增強了 SSL/TLS 和 Client 憑證端點,以納入允許您設定憑證有效天數的新 validity_days 參數。

參數優先順序注意事項:如果您在您的要求中納入一個以上的憑證有效期限參數,我們會以此順順序排列憑證有效期限參數的優先順序。custom_expiration_date > validity_days > validity_years。

關於 DigiCert Services API 文件,請參閱 CertCentral API

new

我們新增了新的訂單管理 - 列出訂單重新發行 API 端點,允許您檢視用於憑證訂單的所有重新發行憑證。請參閱列出訂單重新發行端點。

十月 6, 2017

new

新增了新的「擷取訂單驗證」端點;允許您檢視特定訂單的 DCV 和組織驗證的狀態。

/services/v2/order/certificate/{order_id}/validation

更多詳細資料 »

十月 3, 2017

new

在憑證要求 API 端點中新增了新的中繼憑證發行功能。請參閱 CertCentral 中繼憑證發行功能

new

"說明" (?) 下拉功能表包括的新功能;新增了到變更記錄頁面的連結。

fix

修復「訂單詳細資料」端點的 API 漏洞。回應本文現在傳回用戶端憑證的兩個續訂欄位:

"is_renewal": false
"renewed_order_id": 1234567

更多詳細資料 »