<?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: Questions about how to implement always on Primsa access VPN in Prisma Access Discussions</title>
    <link>https://live.paloaltonetworks.com/t5/prisma-access-discussions/questions-about-how-to-implement-always-on-primsa-access-vpn/m-p/1267239#M1336</link>
    <description>&lt;P&gt;See&amp;nbsp;&lt;A href="https://docs.paloaltonetworks.com/ngfw/help/12-1/globalprotect/network-globalprotect-portals/globalprotect-portals-agent-configuration-tab/globalprotect-portals-agent-config-selection-criteria-tab" target="_blank"&gt;GlobalProtect Portals Agent Config Selection Criteria Tab&lt;/A&gt;&amp;nbsp;and maybe use AD&amp;nbsp; group as all the users that need to not use pre-logon to be in that group.&lt;/P&gt;</description>
    <pubDate>Wed, 28 Oct 2026 14:24:18 GMT</pubDate>
    <dc:creator>nikoolayy1</dc:creator>
    <dc:date>2026-10-28T14:24:18Z</dc:date>
    <item>
      <title>Questions about how to implement always on Primsa access VPN</title>
      <link>https://live.paloaltonetworks.com/t5/prisma-access-discussions/questions-about-how-to-implement-always-on-primsa-access-vpn/m-p/1265993#M1334</link>
      <description>&lt;P&gt;We are looking to move all devices that connect to our Prisma Access environment to move to always on VPN. We attempted to do this once and caused the clients to black hole traffic. We are looking to use our internal certificate authority and each device has its own signed certificate for authentication for pre-logon. Is&amp;nbsp; there a way we can limit which devices do pre-logon without enabling always on VPN for all users?&lt;/P&gt;
&lt;P&gt;I was looking at the portal and gateway order for authentication for clients. I dont see an option to have a subnet just for pre-logon.&lt;/P&gt;
&lt;P&gt;I want to be able to limit the scope for testing without impacting everyone.&lt;/P&gt;</description>
      <pubDate>Mon, 12 Oct 2026 13:19:46 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/prisma-access-discussions/questions-about-how-to-implement-always-on-primsa-access-vpn/m-p/1265993#M1334</guid>
      <dc:creator>J.Keefe</dc:creator>
      <dc:date>2026-10-12T13:19:46Z</dc:date>
    </item>
    <item>
      <title>Re: Questions about how to implement always on Primsa access VPN</title>
      <link>https://live.paloaltonetworks.com/t5/prisma-access-discussions/questions-about-how-to-implement-always-on-primsa-access-vpn/m-p/1267239#M1336</link>
      <description>&lt;P&gt;See&amp;nbsp;&lt;A href="https://docs.paloaltonetworks.com/ngfw/help/12-1/globalprotect/network-globalprotect-portals/globalprotect-portals-agent-configuration-tab/globalprotect-portals-agent-config-selection-criteria-tab" target="_blank"&gt;GlobalProtect Portals Agent Config Selection Criteria Tab&lt;/A&gt;&amp;nbsp;and maybe use AD&amp;nbsp; group as all the users that need to not use pre-logon to be in that group.&lt;/P&gt;</description>
      <pubDate>Wed, 28 Oct 2026 14:24:18 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/prisma-access-discussions/questions-about-how-to-implement-always-on-primsa-access-vpn/m-p/1267239#M1336</guid>
      <dc:creator>nikoolayy1</dc:creator>
      <dc:date>2026-10-28T14:24:18Z</dc:date>
    </item>
  </channel>
</rss>

