<?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: PSM Gateway Root Certificate Trusted Issue in PAM Self-Hosted Discussions</title>
    <link>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/psm-gateway-root-certificate-trusted-issue/m-p/1303805#M6759</link>
    <description>&lt;P&gt;@Putmano Keo​&amp;nbsp;Try removing PVWACAFile, that parameter is not documented. Try re-running the container with debug parameters enabled: https://community.cyberark.com/s/article/How-to-enable-debug-logging-for-html5gw-docker-and-podman-version&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Also try a few curl and openssl commands from inside the container and analyze the results + new debug logs generated:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;PSM: openssl s_client -connect &amp;lt;psm-hostname&amp;gt;.&amp;lt;domain&amp;gt;:3389&lt;/P&gt;&lt;P&gt;PVWA: openssl s_client -connect &amp;lt;pvwa-hostname&amp;gt;.&amp;lt;domain&amp;gt;:443&lt;/P&gt;&lt;P&gt;PVWA Curl: curl -iks https://&amp;lt;pvwa-hostname-or-lb&amp;gt;&lt;/P&gt;</description>
    <pubDate>Wed, 04 Feb 2026 22:08:16 GMT</pubDate>
    <dc:creator>CyberArkAlumni</dc:creator>
    <dc:date>2026-02-04T22:08:16Z</dc:date>
    <item>
      <title>PSM Gateway Root Certificate Trusted Issue</title>
      <link>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/psm-gateway-root-certificate-trusted-issue/m-p/1303803#M6757</link>
      <description>&lt;P&gt;I’m trying to install &lt;B&gt;CyberArk PSM Gateway&lt;/B&gt; using &lt;B&gt;Docker on Ubuntu 22.04&lt;/B&gt;, and I’m running into an issue with &lt;B&gt;Root CA trust&lt;/B&gt; between &lt;B&gt;PVWA&lt;/B&gt; and &lt;B&gt;PSM Gateway&lt;/B&gt;.&lt;/P&gt;&lt;P&gt;We are using an &lt;B&gt;internal CA issued by Microsoft Active Directory Certificate Services&lt;/B&gt;. I have placed the Root CA certificate inside the container directory &lt;B&gt;/opt/cert. &lt;/B&gt;I start the PSM Gateway container using this directory for certificate import.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;I&gt;sudo ./html5_console.sh run -ti -p 443:8443 -v /opt/cert/:/opt/import:ro --cap-drop=all--cap-add={CHOWN,DAC_OVERRIDE,FOWNER,SETGID,SETUID} -e AcceptCyberArkEULA=yes -e GWCert=psmgw.crt -e GWKey=psmgw.key -e GWCAFile=rootCA.crt -e PVWACAFile=rootCA.crt -e EndPointAddress=https://pvwa.lab-env.net/PasswordVault --name psmgw.lab-env.net cahtml5gw:14_6_1_8&lt;/I&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I have tested the Root CA in both &lt;B&gt;.crt &lt;/B&gt;and &lt;B&gt;.pem &lt;/B&gt;formats. The PSM Gateway starts successfully, and the certificate import process completes without errors. However, when I try to run "curl &lt;I&gt;https://pvwa.lab-env.net/&lt;/I&gt;" from inside the container, I receive an &lt;B&gt;SSL certificate verification error&lt;/B&gt; indicating that the Root CA is not trusted.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Has anyone faced a similar issue with Root CA trust when running CyberArk PSM Gateway in Docker? Any guidance on the correct way to install or trust the internal Root CA inside the container would be greatly appreciated.&lt;/P&gt;</description>
      <pubDate>Wed, 04 Feb 2026 16:22:50 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/psm-gateway-root-certificate-trusted-issue/m-p/1303803#M6757</guid>
      <dc:creator>P.Keo122631153060</dc:creator>
      <dc:date>2026-02-04T16:22:50Z</dc:date>
    </item>
    <item>
      <title>Re: PSM Gateway Root Certificate Trusted Issue</title>
      <link>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/psm-gateway-root-certificate-trusted-issue/m-p/1303804#M6758</link>
      <description>&lt;P&gt;The files under /opt/cert, what permissions do they have?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I have seen this when the files are owned by root and not readable by others. In the container another account (don't remember which) will try to read the pem files, but they still belong to root, so it will fail to read them.&lt;/P&gt;</description>
      <pubDate>Wed, 04 Feb 2026 17:34:49 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/psm-gateway-root-certificate-trusted-issue/m-p/1303804#M6758</guid>
      <dc:creator>Fairlane</dc:creator>
      <dc:date>2026-02-04T17:34:49Z</dc:date>
    </item>
    <item>
      <title>Re: PSM Gateway Root Certificate Trusted Issue</title>
      <link>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/psm-gateway-root-certificate-trusted-issue/m-p/1303805#M6759</link>
      <description>&lt;P&gt;@Putmano Keo​&amp;nbsp;Try removing PVWACAFile, that parameter is not documented. Try re-running the container with debug parameters enabled: https://community.cyberark.com/s/article/How-to-enable-debug-logging-for-html5gw-docker-and-podman-version&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Also try a few curl and openssl commands from inside the container and analyze the results + new debug logs generated:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;PSM: openssl s_client -connect &amp;lt;psm-hostname&amp;gt;.&amp;lt;domain&amp;gt;:3389&lt;/P&gt;&lt;P&gt;PVWA: openssl s_client -connect &amp;lt;pvwa-hostname&amp;gt;.&amp;lt;domain&amp;gt;:443&lt;/P&gt;&lt;P&gt;PVWA Curl: curl -iks https://&amp;lt;pvwa-hostname-or-lb&amp;gt;&lt;/P&gt;</description>
      <pubDate>Wed, 04 Feb 2026 22:08:16 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/psm-gateway-root-certificate-trusted-issue/m-p/1303805#M6759</guid>
      <dc:creator>CyberArkAlumni</dc:creator>
      <dc:date>2026-02-04T22:08:16Z</dc:date>
    </item>
    <item>
      <title>Re: PSM Gateway Root Certificate Trusted Issue</title>
      <link>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/psm-gateway-root-certificate-trusted-issue/m-p/1303806#M6760</link>
      <description>&lt;P&gt;I have similar issue before, and base on community discussion, i solve it with this setup:&lt;/P&gt;&lt;CODE&gt;sudo ./html5_console.sh run -ti -p 443:8443 -v /opt/cert/:/opt/import:ro -e AcceptCyberArkEULA=yes -e GWCert=psmgw.crt -e GWKey=psmgw.key -e GWCAFile=rootCA.crt -e EndPointAddress=https://&amp;lt;PVWA hostname&amp;gt;/passwordvault --name &amp;lt;container_name&amp;gt; cahtml5gw:&amp;lt;version_tag&amp;gt;&lt;/CODE&gt;&lt;P&gt;Inside the cert directory i put this files:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;psmgw.key&lt;/LI&gt;&lt;LI&gt;psmgw.cer&lt;/LI&gt;&lt;LI&gt;rootCA.cer&lt;/LI&gt;&lt;LI&gt;rootCA_copy.cer (just duplicate of `rootCA.cer`&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Hope this works for you&lt;/P&gt;</description>
      <pubDate>Thu, 05 Feb 2026 01:57:22 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/psm-gateway-root-certificate-trusted-issue/m-p/1303806#M6760</guid>
      <dc:creator>heron.sidabutar</dc:creator>
      <dc:date>2026-02-05T01:57:22Z</dc:date>
    </item>
    <item>
      <title>Re: PSM Gateway Root Certificate Trusted Issue</title>
      <link>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/psm-gateway-root-certificate-trusted-issue/m-p/1303807#M6761</link>
      <description>&lt;P&gt;I have fixed the permission but it still the same.&lt;/P&gt;</description>
      <pubDate>Thu, 05 Feb 2026 14:43:14 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/psm-gateway-root-certificate-trusted-issue/m-p/1303807#M6761</guid>
      <dc:creator>P.Keo122631153060</dc:creator>
      <dc:date>2026-02-05T14:43:14Z</dc:date>
    </item>
    <item>
      <title>Re: PSM Gateway Root Certificate Trusted Issue</title>
      <link>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/psm-gateway-root-certificate-trusted-issue/m-p/1303808#M6762</link>
      <description>&lt;P&gt;I have run the debug, but I cannot open it to read. Is it a text file? Thanks.&lt;/P&gt;</description>
      <pubDate>Thu, 05 Feb 2026 14:43:55 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/psm-gateway-root-certificate-trusted-issue/m-p/1303808#M6762</guid>
      <dc:creator>P.Keo122631153060</dc:creator>
      <dc:date>2026-02-05T14:43:55Z</dc:date>
    </item>
    <item>
      <title>Re: PSM Gateway Root Certificate Trusted Issue</title>
      <link>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/psm-gateway-root-certificate-trusted-issue/m-p/1303809#M6763</link>
      <description>&lt;P&gt;Thank you, Heron. Yes, I fixed it by duplicating rootCA.pem and rootCA2.pem. Do you know why this is necessary? Is this a bug? I used to deploy on version 12.6, and I didn’t have this issue.&lt;/P&gt;</description>
      <pubDate>Thu, 05 Feb 2026 14:46:29 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/psm-gateway-root-certificate-trusted-issue/m-p/1303809#M6763</guid>
      <dc:creator>P.Keo122631153060</dc:creator>
      <dc:date>2026-02-05T14:46:29Z</dc:date>
    </item>
  </channel>
</rss>

