<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: PTA - Root CA Import Fail &amp;quot;Certificate is not valid or signature algorithm is not at least SHA256&amp;quot; in PAM Self-Hosted Discussions</title>
    <link>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/pta-root-ca-import-fail-quot-certificate-is-not-valid-or/m-p/1417751#M87009</link>
    <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;The root certificate we are testing is available in two formats:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;RootCA.crt (PEM encoded)&lt;/LI&gt;&lt;LI&gt;RootCA.cer (DER encoded)&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;Both commands returned exactly the same certificate details (Issuer, Subject, Serial Number, Validity, etc.), confirming that they contain the same certificate with different encodings.&lt;/P&gt;&lt;P&gt;I tested both files with the PTA utility and received the same error in both cases&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Is there a specific file extension, encoding, certificate attribute, or Key Usage combination that PTA expects for Root CA certificates?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Wed, 22 Jul 2026 13:51:46 GMT</pubDate>
    <dc:creator>ACatalano</dc:creator>
    <dc:date>2026-07-22T13:51:46Z</dc:date>
    <item>
      <title>PTA - Root CA Import Fail "Certificate is not valid or signature algorithm is not at least SHA256"</title>
      <link>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/pta-root-ca-import-fail-quot-certificate-is-not-valid-or/m-p/1417748#M87006</link>
      <description>&lt;P&gt;Hello everyone,&lt;/P&gt;&lt;P&gt;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&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The utility immediately returns: &lt;I&gt;An error occurred while importing root certificate. Certificate is not valid or signature algorithm is not at least SHA256.&lt;/I&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The certificate being imported is a Microsoft ADCS Enterprise Root CA certificate.&lt;/P&gt;&lt;P&gt;I have verified that:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;The certificate is a valid Root CA&lt;/LI&gt;&lt;LI&gt;CA:TRUE&lt;/LI&gt;&lt;LI&gt;The signature algorithm issha256WithRSAEncryption&lt;/LI&gt;&lt;LI&gt;The key size is RSA 2048&lt;/LI&gt;&lt;LI&gt;The certificate is successfully parsed and validated by both OpenSSL and Java keytool&lt;/LI&gt;&lt;LI&gt;The certificate does not use RSASSA-PSS&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;No additional exception or stack trace is recorded.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Has anyone experienced a similar issue when importing a Microsoft ADCS Root CA certificate into PTA 14.2.x?&lt;/P&gt;&lt;P&gt;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?&lt;/P&gt;&lt;P&gt;Any suggestions would be greatly appreciated.&lt;/P&gt;&lt;P&gt;Thank you.&lt;/P&gt;</description>
      <pubDate>Wed, 15 Jul 2026 08:41:47 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/pta-root-ca-import-fail-quot-certificate-is-not-valid-or/m-p/1417748#M87006</guid>
      <dc:creator>ACatalano</dc:creator>
      <dc:date>2026-07-15T08:41:47Z</dc:date>
    </item>
    <item>
      <title>Re: PTA - Root CA Import Fail "Certificate is not valid or signature algorithm is not at least SHA256"</title>
      <link>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/pta-root-ca-import-fail-quot-certificate-is-not-valid-or/m-p/1417749#M87007</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Take a look at the following information:&lt;/P&gt;&lt;P&gt;https://docs.cyberark.com/pam-self-hosted/14.2/en/content/pta/certificate-requirements.htm?Highlight=certificate%20requirements&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 16 Jul 2026 10:43:33 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/pta-root-ca-import-fail-quot-certificate-is-not-valid-or/m-p/1417749#M87007</guid>
      <dc:creator>CyberArkAlumni</dc:creator>
      <dc:date>2026-07-16T10:43:33Z</dc:date>
    </item>
    <item>
      <title>Re: PTA - Root CA Import Fail "Certificate is not valid or signature algorithm is not at least SHA256"</title>
      <link>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/pta-root-ca-import-fail-quot-certificate-is-not-valid-or/m-p/1417750#M87008</link>
      <description>&lt;P&gt;This refers to PTA's certificate, not the root one.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;@Andrea Catalano​&amp;nbsp;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.&lt;/P&gt;</description>
      <pubDate>Tue, 21 Jul 2026 10:29:54 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/pta-root-ca-import-fail-quot-certificate-is-not-valid-or/m-p/1417750#M87008</guid>
      <dc:creator>Korneliusz_Lis</dc:creator>
      <dc:date>2026-07-21T10:29:54Z</dc:date>
    </item>
    <item>
      <title>Re: PTA - Root CA Import Fail "Certificate is not valid or signature algorithm is not at least SHA256"</title>
      <link>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/pta-root-ca-import-fail-quot-certificate-is-not-valid-or/m-p/1417751#M87009</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;The root certificate we are testing is available in two formats:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;RootCA.crt (PEM encoded)&lt;/LI&gt;&lt;LI&gt;RootCA.cer (DER encoded)&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;Both commands returned exactly the same certificate details (Issuer, Subject, Serial Number, Validity, etc.), confirming that they contain the same certificate with different encodings.&lt;/P&gt;&lt;P&gt;I tested both files with the PTA utility and received the same error in both cases&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Is there a specific file extension, encoding, certificate attribute, or Key Usage combination that PTA expects for Root CA certificates?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 22 Jul 2026 13:51:46 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/pta-root-ca-import-fail-quot-certificate-is-not-valid-or/m-p/1417751#M87009</guid>
      <dc:creator>ACatalano</dc:creator>
      <dc:date>2026-07-22T13:51:46Z</dc:date>
    </item>
  </channel>
</rss>

