<?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 Connect automatically to Global Protect using OKTA cred in General Topics</title>
    <link>https://live.paloaltonetworks.com/t5/general-topics/connect-automatically-to-global-protect-using-okta-cred/m-p/534469#M109982</link>
    <description>&lt;P&gt;Hi,&lt;/P&gt;
&lt;P&gt;Thought it might be worth asking here, maybe you can help me &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;We're using Prisma Access and the Global Protect client to log in to VPN. We're also using OKTA to authenticate.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Is there any way to somehow automate the login to the client, and maybe in a way, somehow enforce the login? We basically want all of our users to keep login into GP without a way to disable it (for security visibility). It should be completely seamless for the user, with as less user intervention as possible.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Right now, we're using an Always-ON mode, with an option to disable the client with only a passcode. That being said, in a restart laptop/cookie expiration, it just pops up the regular OKTA authentication, without anything preventing the user from closing it, and then the client stays on "connecting...".&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Is there anything that you could suggest to me for this to work? Is there anyone here using the pre-logon connection method? is it reliable?&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;*We're also using Jamf Connect, if it matters&lt;/P&gt;</description>
    <pubDate>Wed, 15 Mar 2023 15:13:48 GMT</pubDate>
    <dc:creator>nivhovav</dc:creator>
    <dc:date>2023-03-15T15:13:48Z</dc:date>
    <item>
      <title>Connect automatically to Global Protect using OKTA cred</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/connect-automatically-to-global-protect-using-okta-cred/m-p/534469#M109982</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;
&lt;P&gt;Thought it might be worth asking here, maybe you can help me &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;We're using Prisma Access and the Global Protect client to log in to VPN. We're also using OKTA to authenticate.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Is there any way to somehow automate the login to the client, and maybe in a way, somehow enforce the login? We basically want all of our users to keep login into GP without a way to disable it (for security visibility). It should be completely seamless for the user, with as less user intervention as possible.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Right now, we're using an Always-ON mode, with an option to disable the client with only a passcode. That being said, in a restart laptop/cookie expiration, it just pops up the regular OKTA authentication, without anything preventing the user from closing it, and then the client stays on "connecting...".&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Is there anything that you could suggest to me for this to work? Is there anyone here using the pre-logon connection method? is it reliable?&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;*We're also using Jamf Connect, if it matters&lt;/P&gt;</description>
      <pubDate>Wed, 15 Mar 2023 15:13:48 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/connect-automatically-to-global-protect-using-okta-cred/m-p/534469#M109982</guid>
      <dc:creator>nivhovav</dc:creator>
      <dc:date>2023-03-15T15:13:48Z</dc:date>
    </item>
    <item>
      <title>Re: Connect automatically to Global Protect using OKTA cred</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/connect-automatically-to-global-protect-using-okta-cred/m-p/534474#M109983</link>
      <description>&lt;P&gt;Haven't mentioned but we're using macOS&lt;/P&gt;</description>
      <pubDate>Wed, 15 Mar 2023 15:30:05 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/connect-automatically-to-global-protect-using-okta-cred/m-p/534474#M109983</guid>
      <dc:creator>nivhovav</dc:creator>
      <dc:date>2023-03-15T15:30:05Z</dc:date>
    </item>
    <item>
      <title>Re: Connect automatically to Global Protect using OKTA cred</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/connect-automatically-to-global-protect-using-okta-cred/m-p/534600#M109994</link>
      <description>&lt;P&gt;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/258425"&gt;@nivhovav&lt;/a&gt;,&lt;/P&gt;
&lt;P&gt;You might want to think about changing over to a certificate for the actual tunnel and then using an authentication policy to capture the actual login instead. This would ensure that the tunnel is always connected, while still giving you the ability to enforce user authentication to capture the user-id and access resources.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 15 Mar 2023 20:34:24 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/connect-automatically-to-global-protect-using-okta-cred/m-p/534600#M109994</guid>
      <dc:creator>BPry</dc:creator>
      <dc:date>2023-03-15T20:34:24Z</dc:date>
    </item>
  </channel>
</rss>

