<?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 Config from Outside Organization in GlobalProtect Discussions</title>
    <link>https://live.paloaltonetworks.com/t5/globalprotect-discussions/global-protect-config-from-outside-organization/m-p/596332#M5749</link>
    <description>&lt;P&gt;We are currently using Global Protect with the Portal and Gateway on the same firewall and interface, using SAML authentication through Okta with forced MFA.&amp;nbsp; We have a requirement to allow an outside contractor to connect to our VPN for access to a very specific resource.&amp;nbsp; Their authentication method is going to be unique and likely not use SAML....probably LDAP + CAC card.&amp;nbsp; What is the best way to achieve this?&amp;nbsp; My first thought was to create a secondary authentication profile on the portal, then at the gateway assign these users a unique IP range which I can control.&amp;nbsp; That doesn't seem like a great solution, as the first authentication profile brings up the embedded browser to authenticate to Okta.&amp;nbsp; Do I create second portal and gateway using a loopback interface on the same firewall and direct them there?&amp;nbsp; Any suggestions would be appreciated.&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Thu, 29 Aug 2024 18:06:34 GMT</pubDate>
    <dc:creator>DEBARJD</dc:creator>
    <dc:date>2024-08-29T18:06:34Z</dc:date>
    <item>
      <title>Global Protect Config from Outside Organization</title>
      <link>https://live.paloaltonetworks.com/t5/globalprotect-discussions/global-protect-config-from-outside-organization/m-p/596332#M5749</link>
      <description>&lt;P&gt;We are currently using Global Protect with the Portal and Gateway on the same firewall and interface, using SAML authentication through Okta with forced MFA.&amp;nbsp; We have a requirement to allow an outside contractor to connect to our VPN for access to a very specific resource.&amp;nbsp; Their authentication method is going to be unique and likely not use SAML....probably LDAP + CAC card.&amp;nbsp; What is the best way to achieve this?&amp;nbsp; My first thought was to create a secondary authentication profile on the portal, then at the gateway assign these users a unique IP range which I can control.&amp;nbsp; That doesn't seem like a great solution, as the first authentication profile brings up the embedded browser to authenticate to Okta.&amp;nbsp; Do I create second portal and gateway using a loopback interface on the same firewall and direct them there?&amp;nbsp; Any suggestions would be appreciated.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 29 Aug 2024 18:06:34 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/globalprotect-discussions/global-protect-config-from-outside-organization/m-p/596332#M5749</guid>
      <dc:creator>DEBARJD</dc:creator>
      <dc:date>2024-08-29T18:06:34Z</dc:date>
    </item>
    <item>
      <title>Re: Global Protect Config from Outside Organization</title>
      <link>https://live.paloaltonetworks.com/t5/globalprotect-discussions/global-protect-config-from-outside-organization/m-p/596641#M5765</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;If you use SAML auth your can't use another authentication method on the same portal/gateway. Why not just set them up with a vendor/guest account in your Okta and have them log in with that and your MFA? Whats the need for then to authenticate against a different source? Does the Vendor want you to have your VPN authenticate against their authentication system?&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 03 Sep 2024 18:34:54 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/globalprotect-discussions/global-protect-config-from-outside-organization/m-p/596641#M5765</guid>
      <dc:creator>Claw4609</dc:creator>
      <dc:date>2024-09-03T18:34:54Z</dc:date>
    </item>
  </channel>
</rss>

