<?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: SAML authentication broke after upgrading to pan os 10.1.4-h4 in General Topics</title>
    <link>https://live.paloaltonetworks.com/t5/general-topics/saml-authentication-broke-after-upgrading-to-pan-os-10-1-4-h4/m-p/477271#M103652</link>
    <description>&lt;P&gt;&lt;SPAN&gt;Solution Found:&lt;BR /&gt;&lt;BR /&gt;Looking at the system logs on the PA, this new release is now checking the username being sent in the SAML assertion with the one we are logging in as. Because both of those need to agree with the administrator name, We had to change the Okta Application username format in Credential Details for this Palo Alto app to "Okta username prefix".&amp;nbsp;That change dropped the domain.com from the user name that Okta sent back in the SAML assertion.&lt;/SPAN&gt;&lt;/P&gt;</description>
    <pubDate>Thu, 31 Mar 2022 15:08:21 GMT</pubDate>
    <dc:creator>Akhil_B</dc:creator>
    <dc:date>2022-03-31T15:08:21Z</dc:date>
    <item>
      <title>SAML authentication broke after upgrading to pan os 10.1.4-h4</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/saml-authentication-broke-after-upgrading-to-pan-os-10-1-4-h4/m-p/477255#M103651</link>
      <description>&lt;P&gt;&lt;SPAN&gt;After the upgrade of Pan-OS from 9.1.11 to 10.1.4-h4 last night, our SAML authentication does not work. We have a setup to authenticate the administrators logging into firewall using a SSO SAML profile which redirects to okta and we get authenticated over there.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;It was working totally fine with the 9.1.11 version but as soon as I upgrade to 10.x it stopped working. I followed the step upgrade procedure of palo alto to upgrade 9.1.11 &amp;gt; 10.0.0 &amp;gt; 10.0.9 &amp;gt; 10.1.0 &amp;gt; 10.1.4-h4&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 31 Mar 2022 14:12:54 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/saml-authentication-broke-after-upgrading-to-pan-os-10-1-4-h4/m-p/477255#M103651</guid>
      <dc:creator>Akhil_B</dc:creator>
      <dc:date>2022-03-31T14:12:54Z</dc:date>
    </item>
    <item>
      <title>Re: SAML authentication broke after upgrading to pan os 10.1.4-h4</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/saml-authentication-broke-after-upgrading-to-pan-os-10-1-4-h4/m-p/477271#M103652</link>
      <description>&lt;P&gt;&lt;SPAN&gt;Solution Found:&lt;BR /&gt;&lt;BR /&gt;Looking at the system logs on the PA, this new release is now checking the username being sent in the SAML assertion with the one we are logging in as. Because both of those need to agree with the administrator name, We had to change the Okta Application username format in Credential Details for this Palo Alto app to "Okta username prefix".&amp;nbsp;That change dropped the domain.com from the user name that Okta sent back in the SAML assertion.&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 31 Mar 2022 15:08:21 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/saml-authentication-broke-after-upgrading-to-pan-os-10-1-4-h4/m-p/477271#M103652</guid>
      <dc:creator>Akhil_B</dc:creator>
      <dc:date>2022-03-31T15:08:21Z</dc:date>
    </item>
  </channel>
</rss>

