PTA - Root CA Import Fail "Certificate is not valid or signature algorithm is not at least SHA256"

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Announcements

Welcome Idira to LIVEcommunity!

Our community just got stronger! Explore new identity security resources, connect with experts, and discover more ways to learn and collaborate.

Meet Idira

PTA - Root CA Import Fail "Certificate is not valid or signature algorithm is not at least SHA256"

L1 Bithead

Hello everyone,

I am currently deploying PTA 14.2.5 on RHEL 9.3 and I am encountering an issue while importing the Root CA certificate using sslClientCertificateChainInstallationUtil.sh

 

The utility immediately returns: An error occurred while importing root certificate. Certificate is not valid or signature algorithm is not at least SHA256.

 

The certificate being imported is a Microsoft ADCS Enterprise Root CA certificate.

I have verified that:

  • The certificate is a valid Root CA
  • CA:TRUE
  • The signature algorithm issha256WithRSAEncryption
  • The key size is RSA 2048
  • The certificate is successfully parsed and validated by both OpenSSL and Java keytool
  • The certificate does not use RSASSA-PSS

 

No additional exception or stack trace is recorded.

 

Has anyone experienced a similar issue when importing a Microsoft ADCS Root CA certificate into PTA 14.2.x?

Are there any undocumented certificate requirements, extension requirements, or known limitations with Microsoft Enterprise Root CA certificates that could cause PTA to reject an otherwise valid SHA256 Root CA certificate?

Any suggestions would be greatly appreciated.

Thank you.

3 REPLIES 3

L0 Member

Hi,

 

Take a look at the following information:

https://docs.cyberark.com/pam-self-hosted/14.2/en/content/pta/certificate-requirements.htm?Highlight=certificate%20requirements

 

Regards

 

This refers to PTA's certificate, not the root one.

 

@Andrea Catalano​ What is the root cert's file extension which you are trying to upload? I think you should take a look at this as I remember PTA could be quite sensitive for certificate's file extension.

Hi,

The root certificate we are testing is available in two formats:

  • RootCA.crt (PEM encoded)
  • RootCA.cer (DER encoded)

Both commands returned exactly the same certificate details (Issuer, Subject, Serial Number, Validity, etc.), confirming that they contain the same certificate with different encodings.

I tested both files with the PTA utility and received the same error in both cases

 

Is there a specific file extension, encoding, certificate attribute, or Key Usage combination that PTA expects for Root CA certificates?

 

Regards

 

  • 88 Views
  • 3 replies
  • 0 Likes
Like what you see?

Show your appreciation!

Click Like if a post is helpful to you or if you just want to show your support.

Click Accept as Solution to acknowledge that the answer to your question has been provided.

The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!

These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!

The LIVEcommunity thanks you for your participation!