<?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 VPN portal migration to Cloud in GlobalProtect Discussions</title>
    <link>https://live.paloaltonetworks.com/t5/globalprotect-discussions/vpn-portal-migration-to-cloud/m-p/436469#M1824</link>
    <description>&lt;P&gt;Hi Team&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;We have a GP portal vpn.example.com which is hosted on a physical NGFW where we use SAML for authentication.&lt;/P&gt;&lt;P&gt;Now we want to move it to cloud, hence we have to generate a new SAML&amp;nbsp; for this portal IP with the FQDN vpn.example.com.&lt;/P&gt;&lt;P&gt;We want to use the same FQDN for GP portal on cloud. I am not sure about the IDP (SAML) side configuration but I believe they map the SAML file with FQDN/IP.&lt;/P&gt;&lt;P&gt;How do I proceed in this case if I want to test the new cloud GP portal setup because if I generate new SAML with this FQDN it will mess up my existing GP portal setup.&lt;/P&gt;&lt;P&gt;Please correct me if i am wrong.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Fri, 24 Sep 2021 13:44:43 GMT</pubDate>
    <dc:creator>shubhamgupta</dc:creator>
    <dc:date>2021-09-24T13:44:43Z</dc:date>
    <item>
      <title>VPN portal migration to Cloud</title>
      <link>https://live.paloaltonetworks.com/t5/globalprotect-discussions/vpn-portal-migration-to-cloud/m-p/436469#M1824</link>
      <description>&lt;P&gt;Hi Team&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;We have a GP portal vpn.example.com which is hosted on a physical NGFW where we use SAML for authentication.&lt;/P&gt;&lt;P&gt;Now we want to move it to cloud, hence we have to generate a new SAML&amp;nbsp; for this portal IP with the FQDN vpn.example.com.&lt;/P&gt;&lt;P&gt;We want to use the same FQDN for GP portal on cloud. I am not sure about the IDP (SAML) side configuration but I believe they map the SAML file with FQDN/IP.&lt;/P&gt;&lt;P&gt;How do I proceed in this case if I want to test the new cloud GP portal setup because if I generate new SAML with this FQDN it will mess up my existing GP portal setup.&lt;/P&gt;&lt;P&gt;Please correct me if i am wrong.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 24 Sep 2021 13:44:43 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/globalprotect-discussions/vpn-portal-migration-to-cloud/m-p/436469#M1824</guid>
      <dc:creator>shubhamgupta</dc:creator>
      <dc:date>2021-09-24T13:44:43Z</dc:date>
    </item>
    <item>
      <title>Re: VPN portal migration to Cloud</title>
      <link>https://live.paloaltonetworks.com/t5/globalprotect-discussions/vpn-portal-migration-to-cloud/m-p/436643#M1828</link>
      <description>&lt;P&gt;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/193747"&gt;@shubhamgupta&lt;/a&gt;,&lt;/P&gt;&lt;P&gt;You would need to look at your IDP and see how they actually handle the authentication on their side of things to see if the attempt coming from a new IP would actually matter. In some instances it would, but in others the IP that services the request has literally no bearing and its all handled via certificates.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Sun, 26 Sep 2021 03:40:44 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/globalprotect-discussions/vpn-portal-migration-to-cloud/m-p/436643#M1828</guid>
      <dc:creator>BPry</dc:creator>
      <dc:date>2021-09-26T03:40:44Z</dc:date>
    </item>
  </channel>
</rss>

