Filtraggio per: tls certificates x cancella
new

Upcoming Schedule Maintenance

Update: There is no planned downtime during maintenance on May 7, MDT (May 8, UTC).

DigiCert will perform scheduled maintenance on May 7, 2022, between 22:00 – 24:00 MDT (May 8, 2022, between 04:00 – 06:00 UTC). Although we have redundancies to protect your services, some DigiCert services may be unavailable during this time.

What can I do?

Plan accordingly:

  • Schedule high-priority orders, renewals, and reissues before or after the maintenance window.
  • Expect interruptions if you use the APIs for immediate certificate issuance and automated tasks.
  • To get live maintenance updates, subscribe to the DigiCert Status page. This subscription includes email alerts for when maintenance begins and when it ends.
  • See the DigiCert 2022 maintenance schedule for maintenance dates and times.

Services will be restored as soon as we complete the maintenance.

new

Upcoming Schedule Maintenance

DigiCert will perform scheduled maintenance on April 2, 2022, between 22:00 – 24:00 MDT (April 3, 2022, between 04:00 – 06:00 UTC). During this time, some services may be down for up to two hours.

Note: Maintenance will be one hour earlier for those who don't observe daylight savings.

Infrastructure-related maintenance downtime

We will start this infrastructure-related maintenance at 22:00 MDT (04:00 UTC). Then the services listed below may be down for up to two hours.

CertCentral® TLS certificate issuance:

  • TLS certificate requests submitted during this time will fail
  • Failed requests should be resubmitted after services are restored

CIS and CertCentral® SCEP:

  • Certificate Issuing Service (CIS) will be down
  • CertCentral Simple Certificate Enrollment Protocol (SCEP) will be down
  • Requests submitted during this time will fail
  • CIS APIs will return a "503 Service is unavailable" error
  • Failed requests should be resubmitted after services are restored

Direct Cert Portal new domain and organization validation:

  • New domains submitted for validation during this time will fail
  • New organizations submitted for validation during this time will fail
  • Failed requests should be resubmitted after services are restored

QuoVadis® TrustLink® certificate issuance:

  • TrustLink certificate requests submitted during this time will be delayed
  • Requests will be added to a queue for processing later
  • Queued-up requests will be processed after services are restored

PKI Platform 8 new domain and organization validation:

  • New domains submitted for validation during this time will fail
  • New organizations submitted for validation during this time will fail
  • Requests will be added to a queue for processing later
  • Queued-up requests will be processed after services are restored
  • Access to User Authorization Agent (UAA) services will be disabled: both the UAA Admin and User web portals

What can I do?

Plan accordingly:

  • Schedule high-priority orders, renewals, and reissues before or after the maintenance window.
  • Expect interruptions if you use the APIs for immediate certificate issuance and automated tasks.
  • To get live maintenance updates, subscribe to the DigiCert Status page. This subscription includes email alerts for when maintenance begins and when it ends.
  • For scheduled maintenance dates and times, see DigiCert 2022 scheduled maintenance.

Services will be restored as soon as we complete the maintenance.

new

Upcoming Schedule Maintenance

DigiCert will perform scheduled maintenance on March 5, 2022, between 22:00 – 24:00 MST (March 6, 2022, between 05:00 – 07:00 UTC). During this time, some services may be down for up to two hours.

Infrastructure-related maintenance downtime

We will start this infrastructure-related maintenance at 22:00 MST (05:00 UTC). Then the services listed below may be down for up to two hours.

CertCentral™ TLS certificate issuance:

  • TLS certificate requests submitted during this time will fail
  • Failed requests should be resubmitted after services are restored

CIS and CertCentral™ SCEP:

  • Certificate Issuing Service (CIS) will be down
  • CertCentral Simple Certificate Enrollment Protocol (SCEP) will be down
  • Requests submitted during this time will fail
  • CIS APIs will return a "503 Service is unavailable" error
  • Failed requests should be resubmitted after services are restored

Direct Cert Portal new domain and organization validation:

  • New domains submitted for validation during this time will fail
  • New organizations submitted for validation during this time will fail
  • Failed requests should be resubmitted after services are restored

QuoVadis™ TrustLink™ certificate issuance:

  • TrustLink certificate requests submitted during this time will be delayed
  • Requests will be added to a queue for processing later
  • Queued-up requests will be processed after services are restored

PKI Platform 8 new domain and organization validation:

  • New domains submitted for validation during this time will fail
  • New organizations submitted for validation during this time will fail
  • Requests will be added to a queue for processing later
  • Queued-up requests will be processed after services are restored

What can I do?

Plan accordingly:

  • Schedule high-priority orders, renewals, and reissues before or after the maintenance window.
  • Expect interruptions if you use the APIs for immediate certificate issuance and automated tasks.
  • To get live maintenance updates, subscribe to the DigiCert Status page. This subscription includes email alerts for when maintenance begins and when it ends.
  • For scheduled maintenance dates and times, see DigiCert 2022 scheduled maintenance.

Services will be restored as soon as we complete the maintenance.

compliance

Industry changes to file-based DCV (HTTP Practical Demonstration, file auth, file, HTTP token, and HTTP auth)

To comply with new industry standards for the file-based domain control validation (DCV) method, you can only use the file-based DCV to demonstrate control over fully qualified domain names (FQDNs), exactly as named.

To learn more about the industry change, see Domain validation policy changes in 2021.

How does this affect me?

As of November 16, 2021, you must use one of the other supported DCV methods, such as Email, DNS TXT, and CNAME, to:

  • Validate wildcard domains (*.example.com)
  • To include subdomains in the domain validation when validating the higher-level domain. For example, if you want to cover www.example.com, when you validate the higher-level domain, example.com.
  • Prevalidate entire domains and subdomains.

To learn more about the supported DCV method for DV, OV, and EV certificate requests:

compliance

CertCentral: Pending certificate requests and domain prevalidation using file-based DCV

Pending certificate request

If you have a pending certificate request with incomplete file-based DCV checks, you may need to switch DCV methods* or use the file-based DCV method to demonstrate control over every fully qualified domain name, exactly as named, on the request.

*Note: For certificate requests with incomplete file-based DCV checks for wildcard domains, you must use a different DCV method.

To learn more about the supported DCV methods for DV, OV, and EV certificate requests:

Domain prevalidation

If you plan to use the file-based DCV method to prevalidate an entire domain or entire subdomain, you must use a different DCV method.

To learn more about the supported DCV methods for domain prevalidation, see Supported domain control validation (DCV) methods for domain prevalidation.

compliance

CertCentral Services API

If you use the CertCentral Services API to order certificates or submit domains for prevalidation using file-based DCV (http-token), this change may affect your API integrations. To learn more, visit File-based domain control validation (http-token).

fix

Risoluzione del bug: Certificato DV non allegato alla notifica e-mail

Abbiamo risolto un bug nel processo di emissione del certificato DV in cui non allegavamo una copia del certificato DV alla notifica e-mail Il tuo certificato per il tuo dominio. Come risoluzione temporanea a questo problema, ora includiamo un link per il download del certificato nella notifica di e-mail certificato DV.

Nota: Dopo che DigiCert emette un certificato, è immediatamente disponibile nel tuo account CertCentral.

Per usare il link per il download nell’e-mail, devi avere accesso all’account CertCentral e avere le autorizzazioni per accedere all’ordine di certificato.

Se il destinatario dell’e-mail non ha accesso all’account o all’ordine di certificato, puoi inviare per e-mail una copia del certificato DV dal tuo account CertCentral. Consulta le nostre istruzioni per come inviare per e-mail un certificato DV dal tuo account CertCentral.

enhancement

Upgrade account partner precedenti a CertCentral

Nella DigiCert Service API, abbiamo aggiornato l’endpoint—ID ordine DigiCert—per facilitare la ricerca degli ID ordine DigiCert corrispondenti per i tuoi ordini di certificato TLS/SSL GeoTrust precedenti migrati.

Adesso, puoi usare l’ID* ordine GeoTrust per accedere all’ID ordine DigiCert per i tuoi ordini certificato GeoTrust. Inoltre, quando si usa l’ID ordine GeoTrust, riportiamo l’ID ordine certificato DigiCert più attuale.

*Nota: Negli account partner precedente, hai accesso solamente all’ID ordine GeoTrust per i tuoi ordini di certificati TLS/SSL GeoTrust.

Background

Dopo che migri gli ordini di certificato SSL/TLS pubblici attivi al tuo nuovo account, assegniamo un ID ordine DigiCert univoco a ogni ordine di certificato SSL/TLS precedente migrato.

Per ulteriori informazioni:

fix

Abbiamo risolto un bug in CertCentral dove le organizzazioni "nascoste" impedivano l’apertura dei moduli di richiesta certificato. Per risolvere questo problema, non includiamo più le organizzazione nascoste nell’elenco delle organizzazioni disponibili sui moduli di richiesta certificato.

Cosa accade se voglio aggiungere un’organizzazione "nascosta" ad una richiesta di certificato?

Per includere un’organizzazione "nascosta" nell’elenco delle organizzazioni disponibili sui tuoi moduli di richiesta certificato , basta mostrarla.

  1. Nel menu principale sinistro, vai su Certificati > Organizzazioni.
  2. Nella pagina Organizzazioni, nel menu a discesa Organizzazioni nascoste, seleziona Mostra, quindi fai clic su Vai.
  3. Fai clic sull’organizzazione che vuoi mostrare.
  4. Nella pagina dei dettagli dell’organizzazione, fai clic su Mostra.

La prossima volta che ordini un certificato, l’organizzazione sarà visualizzata nell’elenco delle organizzazioni disponibili sul modulo di richiesta certificato.

Nota: Questa modifica interessa solo l’interfaccia utente (IU) CertCentral. L’API supporta l’aggiunta di organizzazioni "nascoste" alle tue richieste; non devi mostrare un’organizzazione per aggiungerla ad una richiesta certificato.

new

Upgrade account precedenti a CertCentral

Nella DigiCert Service API, abbiamo aggiunto un nuovo endpoint—ID ordine DigiCert—per facilitare la ricerca degli ID ordine DigiCert corrispondenti per i tuoi ordini Symantec precedenti migrati.

Dopo che migri gli ordini di certificato SSL/TLS pubblici attivi al tuo nuovo account, assegniamo un ID ordine DigiCert univoco a ogni ordine di certificato SSL/TLS Symantec precedente migrato.

Esempio di richiesta

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

Esempio di risposta
200 OK

Example response for Digicert order ID endpoint

Per ulteriori informazioni:

new

Upgrade 2.0 account precedenti

Siamo lieti di annunciare che i domini convalidati e i certificati SSL/TLS pubblici attivi ora sono inclusi nella migrazione dei dati durante l’upgrade della console precedente a CertCentral. Consulta Cosa devi sapere sulla migrazione dei dati account.

Con questo rilascio, avviamo un upgrade in fasi a CertCentral delle nostre console precedenti. I criteri di upgrade dipendono dalla dimensione dell'azienda, dalle preferenze di valuta e dall’uso delle funzioni.

Nota: Gli upgrade CertCentral sono gratuiti. Se sei interessato ad eseguire l’upgrade adesso, contatta il tuo account manager o il nostro team di assistenza.

Se il tuo account precedente soddisfa i criteri della fase uno, quando accedi alla console, vedrai un’opzione per eseguire l’upgrade a CertCentral. Al momento dell’upgrade, migriamo le tue organizzazioni e i domini convalidati al tuo account CertCentral. Dopodiché, quando sei pronto, puoi importare i tuoi certificati SSL/TLS pubblici attivi.

Per ulteriori informazioni sull’upgrade a CertCentral e sulla migrazione dei dati, consulta la nostra guida all’Upgrade a CertCentral.

Altri tipi di certificati

SSL privati, firma codice, S/Mime e altri tipi di certificati non possono essere importati in questo momento. Il certificato SSL/TLS e non SSL/TLS provato farà parte di una migrazione separata.