<?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 PKIX path building failed: unable to find valid certification path to requested target in General Topics</title>
    <link>https://live.paloaltonetworks.com/t5/general-topics/pkix-path-building-failed-unable-to-find-valid-certification/m-p/1249622#M126111</link>
    <description>&lt;P&gt;hello guys ,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;i have a tomcat app linux server that connect to central bank endpoint using global protect client to establish the connection , the endpoint is using self signed cert and i get this error&lt;/P&gt;</description>
    <pubDate>Fri, 06 Mar 2026 19:24:26 GMT</pubDate>
    <dc:creator>altamimi</dc:creator>
    <dc:date>2026-03-06T19:24:26Z</dc:date>
    <item>
      <title>PKIX path building failed: unable to find valid certification path to requested target</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/pkix-path-building-failed-unable-to-find-valid-certification/m-p/1249622#M126111</link>
      <description>&lt;P&gt;hello guys ,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;i have a tomcat app linux server that connect to central bank endpoint using global protect client to establish the connection , the endpoint is using self signed cert and i get this error&lt;/P&gt;</description>
      <pubDate>Fri, 06 Mar 2026 19:24:26 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/pkix-path-building-failed-unable-to-find-valid-certification/m-p/1249622#M126111</guid>
      <dc:creator>altamimi</dc:creator>
      <dc:date>2026-03-06T19:24:26Z</dc:date>
    </item>
    <item>
      <title>Re: PKIX path building failed: unable to find valid certification path to requested target</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/pkix-path-building-failed-unable-to-find-valid-certification/m-p/1249643#M126113</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/226828141"&gt;@altamimi&lt;/a&gt;&amp;nbsp;,&lt;/P&gt;
&lt;P data-end="309" data-start="256"&gt;&amp;nbsp;&lt;/P&gt;
&lt;P data-end="309" data-start="256"&gt;Let me know if im understanding your setup correctly:&amp;nbsp;&lt;/P&gt;
&lt;P data-end="309" data-start="256"&gt;&amp;nbsp;&lt;/P&gt;
&lt;P data-end="541" data-start="311"&gt;You have a Linux host running a Tomcat app and that host is connected using the GlobalProtect client. In the GP app, you then establish a VPN connection to a Portal/Gateway hosted on the Central Bank network.&lt;/P&gt;
&lt;P data-end="541" data-start="311"&gt;&amp;nbsp;&lt;/P&gt;
&lt;P data-end="758" data-start="543"&gt;Once connected, theTomcat app youre running locally on the linux host needs to connect over to an endpoint on the Central Bank side and that endpoint is using a self-signed cert. However, your connection fails.&amp;nbsp;&lt;/P&gt;
&lt;P data-end="758" data-start="543"&gt;&amp;nbsp;&lt;/P&gt;
&lt;P data-end="758" data-start="543"&gt;If you are getting "&lt;SPAN&gt;PKIX path building failed: unable to find valid certification path to requested target" error on your linux host, then Im suspecting this error is more related to&amp;nbsp;the certificate trust rather than GP and the Security Policies itself. With that being said, what you can do is gather evidence on the Layer 3 and Layer 4 side.&amp;nbsp;&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P data-end="758" data-start="543"&gt;&amp;nbsp;&lt;/P&gt;
&lt;P data-end="758" data-start="543"&gt;&lt;SPAN&gt;What I would do:&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P data-end="758" data-start="543"&gt;&amp;nbsp;&lt;/P&gt;
&lt;P data-end="1232" data-start="1048"&gt;Head to your traffic logs and grab the endpoint URL that the Tomcat app is calling. Resolve that hostname to an IP, then monitor traffic between the Linux host IP and that endpoint IP.&lt;/P&gt;
&lt;P data-end="1390" data-start="1234"&gt;&amp;nbsp;&lt;/P&gt;
&lt;P data-end="1390" data-start="1234"&gt;Initiate the call again while watching the traffic logs. Do you see any blocks or drops? Do you see traffic being allowed with bytes sent but none returned? That should help confirm whether the traffic is successfully traversing the firewall or if something in the policy path is interfering.&lt;/P&gt;
&lt;P data-end="1808" data-start="1532"&gt;&amp;nbsp;&lt;/P&gt;
&lt;P data-end="2146" data-start="1810"&gt;Now my personal .2: I'm assuming that because you are receiving an error response, the traffic is likely being allowed/routing correctly/successfully traveling through bank network. **However, it is still worth validating ALL traffic flows. It could also be that the application has a dependency other than 443. For example, some applications attempt to reach OCSP or CRL endpoints over port 80 to validate certificates. Be really attentive when monitoring the traffic during troubleshooting to make sure you understand ALL flows.&amp;nbsp;&lt;/P&gt;
&lt;P data-end="2146" data-start="1810"&gt;&amp;nbsp;&lt;/P&gt;
&lt;P data-end="2146" data-start="1810"&gt;In the event you find that your firewall is not blocking or dropping the connectivity, that would indicate the traffic is successfully traversing the firewall and the issue likely exists further up the stack.&lt;/P&gt;
&lt;P data-end="2146" data-start="1810"&gt;&amp;nbsp;&lt;/P&gt;
&lt;P data-end="1527" data-start="1392"&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;
&lt;P data-end="758" data-start="543"&gt;&lt;CODE data-end="848" data-start="760"&gt;&lt;/CODE&gt;&lt;/P&gt;
&lt;P data-end="758" data-start="543"&gt;&lt;CODE data-end="848" data-start="760"&gt;&lt;/CODE&gt;&lt;/P&gt;</description>
      <pubDate>Sat, 07 Mar 2026 23:10:29 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/pkix-path-building-failed-unable-to-find-valid-certification/m-p/1249643#M126113</guid>
      <dc:creator>JayGolf</dc:creator>
      <dc:date>2026-03-07T23:10:29Z</dc:date>
    </item>
  </channel>
</rss>

