<?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 SAML for management access to PA in VM-Series in the Public Cloud</title>
    <link>https://live.paloaltonetworks.com/t5/vm-series-in-the-public-cloud/saml-for-management-access-to-pa/m-p/498509#M1572</link>
    <description>&lt;P&gt;Hi folks,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;We got a customer who needs to authenticate firewall admins (PA management) against Azure SAML.&lt;/P&gt;&lt;P&gt;Azure only allows you to specify a unique SSO URL being the type&amp;nbsp;https://&amp;lt;Customer Firewall FQDN&amp;gt;:443/SAML20/SP&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Problem is, this is a standard Active-Passive setup so in case of a failover, the source Customer Firewall FQDN becomes that of the Passive unit, which is not recognized by Azure and thus authentication fails.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Any way we can make this happen? It seems creating an Auth Sequence does not allow to input SAML profiles. The only way we can come up with is creating two separate admins and associate each to a different SAML profile, and at Azure create also two separate profiles?&lt;/P&gt;&lt;P&gt;#saml &lt;LI-PRODUCT title="Azure" id="Azure"&gt;&lt;/LI-PRODUCT&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Thu, 02 Jun 2022 16:38:31 GMT</pubDate>
    <dc:creator>JF18866</dc:creator>
    <dc:date>2022-06-02T16:38:31Z</dc:date>
    <item>
      <title>SAML for management access to PA</title>
      <link>https://live.paloaltonetworks.com/t5/vm-series-in-the-public-cloud/saml-for-management-access-to-pa/m-p/498509#M1572</link>
      <description>&lt;P&gt;Hi folks,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;We got a customer who needs to authenticate firewall admins (PA management) against Azure SAML.&lt;/P&gt;&lt;P&gt;Azure only allows you to specify a unique SSO URL being the type&amp;nbsp;https://&amp;lt;Customer Firewall FQDN&amp;gt;:443/SAML20/SP&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Problem is, this is a standard Active-Passive setup so in case of a failover, the source Customer Firewall FQDN becomes that of the Passive unit, which is not recognized by Azure and thus authentication fails.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Any way we can make this happen? It seems creating an Auth Sequence does not allow to input SAML profiles. The only way we can come up with is creating two separate admins and associate each to a different SAML profile, and at Azure create also two separate profiles?&lt;/P&gt;&lt;P&gt;#saml &lt;LI-PRODUCT title="Azure" id="Azure"&gt;&lt;/LI-PRODUCT&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 02 Jun 2022 16:38:31 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/vm-series-in-the-public-cloud/saml-for-management-access-to-pa/m-p/498509#M1572</guid>
      <dc:creator>JF18866</dc:creator>
      <dc:date>2022-06-02T16:38:31Z</dc:date>
    </item>
  </channel>
</rss>

