<?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: global protect connection failed authentication failed !!! in GlobalProtect Discussions</title>
    <link>https://live.paloaltonetworks.com/t5/globalprotect-discussions/global-protect-connection-failed-authentication-failed/m-p/1248257#M7286</link>
    <description>&lt;P&gt;unfortunately theres not a lot of information to work with here&lt;/P&gt;
&lt;P&gt;did you verify the link with DUO is still 'valid': no expired certificates, no new security policy that blocks access to duo, different NAT, expired service account,...&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Mon, 16 Feb 2026 10:25:27 GMT</pubDate>
    <dc:creator>reaper</dc:creator>
    <dc:date>2026-02-16T10:25:27Z</dc:date>
    <item>
      <title>global protect connection failed authentication failed !!!</title>
      <link>https://live.paloaltonetworks.com/t5/globalprotect-discussions/global-protect-connection-failed-authentication-failed/m-p/1247974#M7280</link>
      <description>&lt;P&gt;Hi All,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;We are currently experiencing the following error when attempting to log into Global Protect ( screenshot attached ).&amp;nbsp; Curiously this is happening after getting prompted via Duo . We are using SAML Identity provider for authentication via DUO . All was working fine&amp;nbsp; until yesterday . The last relevant Global Protect logs make reference to an&amp;nbsp; expired cookie error .&amp;nbsp; Nothing has changed on the Duo side as well the GP config .&amp;nbsp; I have tried to disable the encrypt / decrypt cookie certificate on both the Portal and Gateway , also adjusted some the lifetime settings with no success .&lt;/P&gt;
&lt;P&gt;&amp;nbsp;Has anyone experienced that before ?&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Thank you in advance&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="HThiam_0-1770847291006.png" style="width: 400px;"&gt;&lt;img src="https://live.paloaltonetworks.com/t5/image/serverpage/image-id/70646i68C6C395A6618EFD/image-size/medium?v=v2&amp;amp;px=400" role="button" title="HThiam_0-1770847291006.png" alt="HThiam_0-1770847291006.png" /&gt;&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 11 Feb 2026 22:02:05 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/globalprotect-discussions/global-protect-connection-failed-authentication-failed/m-p/1247974#M7280</guid>
      <dc:creator>H.Thiam</dc:creator>
      <dc:date>2026-02-11T22:02:05Z</dc:date>
    </item>
    <item>
      <title>Re: global protect connection failed authentication failed !!!</title>
      <link>https://live.paloaltonetworks.com/t5/globalprotect-discussions/global-protect-connection-failed-authentication-failed/m-p/1248158#M7284</link>
      <description>&lt;P&gt;Is the clock correct on your firewall? Any changes to the NTP server settings? Is the cookie certificate still valid?&lt;BR /&gt;Is there anything interesting in the gpsvc.log file in the cli when reproducing this issue?&lt;BR /&gt;`less mp-log gpsvc.log` to view this log file&lt;/P&gt;</description>
      <pubDate>Fri, 13 Feb 2026 21:21:47 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/globalprotect-discussions/global-protect-connection-failed-authentication-failed/m-p/1248158#M7284</guid>
      <dc:creator>B.Sanchez392701</dc:creator>
      <dc:date>2026-02-13T21:21:47Z</dc:date>
    </item>
    <item>
      <title>Re: global protect connection failed authentication failed !!!</title>
      <link>https://live.paloaltonetworks.com/t5/globalprotect-discussions/global-protect-connection-failed-authentication-failed/m-p/1248257#M7286</link>
      <description>&lt;P&gt;unfortunately theres not a lot of information to work with here&lt;/P&gt;
&lt;P&gt;did you verify the link with DUO is still 'valid': no expired certificates, no new security policy that blocks access to duo, different NAT, expired service account,...&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 16 Feb 2026 10:25:27 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/globalprotect-discussions/global-protect-connection-failed-authentication-failed/m-p/1248257#M7286</guid>
      <dc:creator>reaper</dc:creator>
      <dc:date>2026-02-16T10:25:27Z</dc:date>
    </item>
    <item>
      <title>Re: global protect connection failed authentication failed !!!</title>
      <link>https://live.paloaltonetworks.com/t5/globalprotect-discussions/global-protect-connection-failed-authentication-failed/m-p/1248921#M7295</link>
      <description>&lt;P&gt;Hi both . I appreciate your feedback , this is now resolved&amp;nbsp; . The only thing that we noticed is that we were unknowingly&amp;nbsp; running the pair of firewall independently&amp;nbsp; in an active active scenario so there must have been some asymmetric routing with the traffic .&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 24 Feb 2026 20:30:49 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/globalprotect-discussions/global-protect-connection-failed-authentication-failed/m-p/1248921#M7295</guid>
      <dc:creator>H.Thiam</dc:creator>
      <dc:date>2026-02-24T20:30:49Z</dc:date>
    </item>
  </channel>
</rss>

