<?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 Global Protect Integration with Azure SAML w/ Multiple Gateways in Next-Generation Firewall Discussions</title>
    <link>https://live.paloaltonetworks.com/t5/next-generation-firewall/global-protect-integration-with-azure-saml-w-multiple-gateways/m-p/593197#M3491</link>
    <description>&lt;P&gt;I'm trying to setup an integration with 2 firewalls at different locations.&amp;nbsp; The portal and 1 gateway reside on 1 of the firewalls, and i've used this:&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;A href="https://knowledgebase.paloaltonetworks.com/KCSArticleDetail?id=kA10g0000008U48CAE" target="_blank"&gt;https://knowledgebase.paloaltonetworks.com/KCSArticleDetail?id=kA10g0000008U48CAE&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;to get that going successfully.&amp;nbsp; The 2nd firewall, which has a certificate w/ a different FQDN, doesn't allow users to connect.&amp;nbsp; My thinking was I needed to create a 2nd enterprise application using the 2nd FQDN or is that not necessarily?&lt;/P&gt;</description>
    <pubDate>Fri, 26 Jul 2024 19:32:47 GMT</pubDate>
    <dc:creator>DJ_1924</dc:creator>
    <dc:date>2024-07-26T19:32:47Z</dc:date>
    <item>
      <title>Global Protect Integration with Azure SAML w/ Multiple Gateways</title>
      <link>https://live.paloaltonetworks.com/t5/next-generation-firewall/global-protect-integration-with-azure-saml-w-multiple-gateways/m-p/593197#M3491</link>
      <description>&lt;P&gt;I'm trying to setup an integration with 2 firewalls at different locations.&amp;nbsp; The portal and 1 gateway reside on 1 of the firewalls, and i've used this:&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;A href="https://knowledgebase.paloaltonetworks.com/KCSArticleDetail?id=kA10g0000008U48CAE" target="_blank"&gt;https://knowledgebase.paloaltonetworks.com/KCSArticleDetail?id=kA10g0000008U48CAE&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;to get that going successfully.&amp;nbsp; The 2nd firewall, which has a certificate w/ a different FQDN, doesn't allow users to connect.&amp;nbsp; My thinking was I needed to create a 2nd enterprise application using the 2nd FQDN or is that not necessarily?&lt;/P&gt;</description>
      <pubDate>Fri, 26 Jul 2024 19:32:47 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/next-generation-firewall/global-protect-integration-with-azure-saml-w-multiple-gateways/m-p/593197#M3491</guid>
      <dc:creator>DJ_1924</dc:creator>
      <dc:date>2024-07-26T19:32:47Z</dc:date>
    </item>
    <item>
      <title>Re: Global Protect Integration with Azure SAML w/ Multiple Gateways</title>
      <link>https://live.paloaltonetworks.com/t5/next-generation-firewall/global-protect-integration-with-azure-saml-w-multiple-gateways/m-p/593899#M3525</link>
      <description>&lt;P&gt;Yeah sounds like the second enterprise application is exactly what you need since you are going to have a different SAML configuration for the other FQDN&lt;/P&gt;</description>
      <pubDate>Fri, 02 Aug 2024 18:39:09 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/next-generation-firewall/global-protect-integration-with-azure-saml-w-multiple-gateways/m-p/593899#M3525</guid>
      <dc:creator>TeemuH</dc:creator>
      <dc:date>2024-08-02T18:39:09Z</dc:date>
    </item>
    <item>
      <title>Re: Global Protect Integration with Azure SAML w/ Multiple Gateways</title>
      <link>https://live.paloaltonetworks.com/t5/next-generation-firewall/global-protect-integration-with-azure-saml-w-multiple-gateways/m-p/593901#M3527</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;What error are you getting when users are trying to connect? You are able to use the same SAML Azure App for multiple GlobalProtect gateways, you just need to add the additional gateways under the Basic SAML configuration urls settings in the Azure app. And have the SAML metadata imported on the gateway firewall.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 02 Aug 2024 18:59:57 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/next-generation-firewall/global-protect-integration-with-azure-saml-w-multiple-gateways/m-p/593901#M3527</guid>
      <dc:creator>Claw4609</dc:creator>
      <dc:date>2024-08-02T18:59:57Z</dc:date>
    </item>
    <item>
      <title>Re: Global Protect Integration with Azure SAML w/ Multiple Gateways</title>
      <link>https://live.paloaltonetworks.com/t5/next-generation-firewall/global-protect-integration-with-azure-saml-w-multiple-gateways/m-p/594733#M3583</link>
      <description>&lt;P&gt;Like Claw is saying you just need to add your additonal gateways in your Azure Entra Global Protec single sign on settings.&lt;/P&gt;
&lt;DIV class="azc-form-labelcontainer azc-text-label azc-text-sublabel-neighbor"&gt;&lt;LABEL id="form-label-id-31" class="azc-form-label" for="form-label-id-31-for" data-bind="untrustedContent: label, attr: { title: 1 === ko.unwrap(overflowMode) &amp;amp;&amp;amp; 'string' === typeof ko.unwrap(label) &amp;amp;&amp;amp; ko.unwrap(label) }"&gt;Identifier (Entity ID)&lt;/LABEL&gt;
&lt;DIV class="azc-required-balloon fxc-base azc-control azc-dockedballoon-requiredwidget azc-dockedballoon-required" data-control="true"&gt;
&lt;DIV class="azc-dockedballoon-anchor" aria-hidden="true"&gt;
&lt;DIV class="azc-required-anchor"&gt;And the&amp;nbsp;
&lt;DIV class="azc-form-labelcontainer azc-text-label azc-text-sublabel-neighbor"&gt;&lt;LABEL id="form-label-id-34" class="azc-form-label" for="form-label-id-34-for" data-bind="untrustedContent: label, attr: { title: 1 === ko.unwrap(overflowMode) &amp;amp;&amp;amp; 'string' === typeof ko.unwrap(label) &amp;amp;&amp;amp; ko.unwrap(label) }"&gt;Reply URL (Assertion Consumer Service URL)&lt;/LABEL&gt;
&lt;DIV class="azc-required-balloon fxc-base azc-control azc-dockedballoon-requiredwidget azc-dockedballoon-required" data-control="true"&gt;
&lt;DIV class="azc-dockedballoon-anchor" aria-hidden="true"&gt;
&lt;DIV class="azc-required-anchor"&gt;&amp;nbsp;&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;DIV id="form-label-id-34-balloon" class="fxc-base azc-control azc-dockedballoon azc-dockedballoon-info" data-control="true" aria-owns="azc-dockedballoon-balloon-azc-dockedballoon-balloon0-025"&gt;
&lt;DIV id="form-label-id-34-anchor" class="azc-dockedballoon-anchor" tabindex="-1" role="button" data-bind="attr: { &amp;quot;aria-hidden&amp;quot; : $ctl._isCheckPopulated() || $ctl._isRequired(), &amp;quot;aria-label&amp;quot;: data._ariaLabel(), &amp;quot;aria-expanded&amp;quot;: data.balloonVisible().toString(), &amp;quot;aria-controls&amp;quot;: data.balloonId }" aria-label="Reply URL (Assertion Consumer Service URL)" aria-expanded="false" aria-controls="azc-dockedballoon-balloon-azc-dockedballoon-balloon0-025" aria-describedby="0070f18c-90a5-4190-938c-357decde71f5" aria-labelledby="form-label-id-34-anchor"&gt;
&lt;DIV class="fxs-portal-svg-secondary azc-fill-hovered-heavy azc-dockedballoon-anchor-target" data-bind="css: { &amp;quot;azc-fill-heavy&amp;quot;: data.balloonVisible() }"&gt;Should contain you gateway url's.&lt;/DIV&gt;
&lt;DIV class="fxs-portal-svg-secondary azc-fill-hovered-heavy azc-dockedballoon-anchor-target" data-bind="css: { &amp;quot;azc-fill-heavy&amp;quot;: data.balloonVisible() }"&gt;Example config for prisma access mobile user gateways can be found on : (your's is similar but then for your own gateways)&lt;/DIV&gt;
&lt;DIV class="fxs-portal-svg-secondary azc-fill-hovered-heavy azc-dockedballoon-anchor-target" data-bind="css: { &amp;quot;azc-fill-heavy&amp;quot;: data.balloonVisible() }"&gt;&lt;A href="https://docs.paloaltonetworks.com/prisma-access/integration/microsoft-integrations-with-prisma-access/azure-ad-saml-authentication-for-mobile-user-deployments/configure-mobile-users-without-cloud-identity-engine" target="_blank"&gt;Configure Mobile Users without Cloud Identity Engine (paloaltonetworks.com).&lt;/A&gt;&lt;/DIV&gt;
&lt;DIV class="fxs-portal-svg-secondary azc-fill-hovered-heavy azc-dockedballoon-anchor-target" data-bind="css: { &amp;quot;azc-fill-heavy&amp;quot;: data.balloonVisible() }"&gt;&amp;nbsp;&lt;/DIV&gt;
&lt;DIV class="fxs-portal-svg-secondary azc-fill-hovered-heavy azc-dockedballoon-anchor-target" data-bind="css: { &amp;quot;azc-fill-heavy&amp;quot;: data.balloonVisible() }"&gt;&amp;nbsp;&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;DIV class="azc-formElementSubLabelContainer"&gt;&amp;nbsp;&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;DIV id="form-label-id-31-balloon" class="fxc-base azc-control azc-dockedballoon azc-dockedballoon-info" data-control="true" aria-owns="azc-dockedballoon-balloon-azc-dockedballoon-balloon0-021"&gt;
&lt;DIV id="form-label-id-31-anchor" class="azc-dockedballoon-anchor" tabindex="-1" role="button" data-bind="attr: { &amp;quot;aria-hidden&amp;quot; : $ctl._isCheckPopulated() || $ctl._isRequired(), &amp;quot;aria-label&amp;quot;: data._ariaLabel(), &amp;quot;aria-expanded&amp;quot;: data.balloonVisible().toString(), &amp;quot;aria-controls&amp;quot;: data.balloonId }" aria-label="Identifier (Entity ID)" aria-expanded="false" aria-controls="azc-dockedballoon-balloon-azc-dockedballoon-balloon0-021" aria-describedby="0070f18c-90a5-4190-938c-357decde71f1" aria-labelledby="form-label-id-31-anchor"&gt;
&lt;DIV class="fxs-portal-svg-secondary azc-fill-hovered-heavy azc-dockedballoon-anchor-target" data-bind="css: { &amp;quot;azc-fill-heavy&amp;quot;: data.balloonVisible() }"&gt;&amp;nbsp;&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;DIV class="azc-formElementSubLabelContainer"&gt;&amp;nbsp;&lt;/DIV&gt;</description>
      <pubDate>Tue, 13 Aug 2024 12:56:11 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/next-generation-firewall/global-protect-integration-with-azure-saml-w-multiple-gateways/m-p/594733#M3583</guid>
      <dc:creator>zGomez</dc:creator>
      <dc:date>2024-08-13T12:56:11Z</dc:date>
    </item>
  </channel>
</rss>

