DigiCert KnowledgeBase - Technical Support-hero

Knowledge Base

Enable support for the TLS 1.2 protocol | PKI Platform 8

Solution ID : SO190721142156
Last Modified : 10/21/2023

Scenario

On August 30, 2021, the PKI Platform 8 will deprecate support for Transport Layer Security (TLS) 1.0 and 1.1.

 

What happens if I don't upgrade to TLS 1.2?

Any applications and services still using the TLS 1.0 and TLS 1.1 protocols to communicate with DigiCert using HTTPS will be unable to enroll, renew, search, or revoke certificates, including PKI Platform 8 on-premises components.

 

Solution 

To align with industry and security best practices and as part of DigiCert's continued effort to maintain a world-class PKI platform, PKI Platform 8 will deprecate support for Transport Layer Security (TLS) 1.0 and 1.1 on August 30, 2021.



What do I need to do?

DigiCert recommends updating dependent crypto libraries used by clients, such as Java and .Net, to a version that supports TLS 1.2.

Enrollment flow

Action required?

Note

Browser-based enrollments

No

The current versions of all major browsers support TLS 1.2.

iOS

No

Already supports TLS 1.2

PKI Client

No

Not affected by the change.

PKI Client for Android

No

Not affected by the change.

DigiCert Desktop Client

No

Not affected by the change.

SCEP Proxy Server

Yes

Ensure you are using a version of Java on your SCEP Proxy Server that supports TLS 1.2.

Local Key Escrow and Recovery Service

No

If you run the DigiCert recommended Java version (JRE v8), which supports TLS 1.2, no action is required.

Microsoft Autoenrollment Server

No

Not affected by the change.

Enrollments using PKI Enterprise Gateway for authentication

Yes

Refer to the PKI Enterprise Gateway section below for details on how to enable support for TLS 1.2.

Third-party integrations

Yes

Contact your vendor to verify their support for TLS 1.2.

PKI Enterprise Gateway

To enable support for TLS 1.2 with PKI Enterprise Gateway version 1.21.1 (or older release), you can modify the registry key or update the .Net Framework.

Note: PKI Enterprise Gateway version 1.22.1 and onwards makes use of TLS 1.2 by default.


Option 1: Modify the Registry Key

Step 1: Stop the Internet Information Server (IIS) instance hosting your RA service.

Step 2: If you use the optional Key Escrow and Recovery Service, stop the Tomcat Web Server hosting it.

Step 3: Add or modify the registry key entry.

Windows Registry Editor Version 5.00

 

 

[HKEY_LOCAL_MACHINE\\SOFTWARE\\Microsoft\\.NETFramework\\v4.0.30319]

 

"SchUseStrongCrypto"=dword:00000001



Step 4: Start IIS instance hosting your RA Service.

Step 5: If you use the optional Key Escrow and Recovery Service, start the Tomcat Web Server hosting it.


Option 2: Update the .Net Framework

Step 1: Stop the Internet Information Server (IIS) instance hosting your RA service.

Step 2: If you are using the optional Key Escrow and Recovery Service, stop the Tomcat Web Server hosting it.

Step 3: Back up the RA Service’s web.config file and add targetFramework="4.7.1" to the httpRuntime tag.

<configuration>

 

   <system.web>

 

      <httpRuntime ... targetFramework="4.7.1" />

 

   </system.web>

 

</configuration>

 

Example of the entire httpRuntime configuration line

<httpRuntime executionTimeout="90" maxRequestLength="1048576" useFullyQualifiedRedirectUrl="false" minFreeThreads="8" minLocalRequestFreeThreads="4" appRequestQueueLimit="100" targetFramework="4.7.1"/>

 

Step 4: Start IIS instance hosting your RA Service.

Step 5: If you use the optional Key Escrow and Recovery Service, start the Tomcat Web Server hosting it.

 

API Integrations

Ensure when communicating with DigiCert's endpoints, you enforce the use of TLS 1.2.

For API integrations with the PKI Platform 8 that use the SOAP or RESTful API interfaces using Java or Microsoft .Net Framework, verify that you are using the minimum required version.

API integration

Minimum required version

Java

Java JRE/JDK 8

.Net Framework

4.7.1

Related articles

PKI Platform 8 Ending Support for TLS 1.0 and 1.1

If you have questions or concerns about making the transition to TLS 1.2 in time, contact your account manager or support team. We're here to help you.