<?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 Switching from GlobalProtect username &amp;amp; password to some sort of SSO solution (on-prem AD only) in GlobalProtect Discussions</title>
    <link>https://live.paloaltonetworks.com/t5/globalprotect-discussions/switching-from-globalprotect-username-amp-password-to-some-sort/m-p/383670#M878</link>
    <description>&lt;P&gt;We have always used username &amp;amp; password for authenticating GlobalProtect (using the user's AD account/password). We always connect GlobalProtect AFTER signing on to Windows first.&amp;nbsp; So how difficult would it be to have GlobalProtect simply query Windows for the user's current signed-on creds to use instead of manually typing them? Essentially something like SSO?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;And is it possible to setup a 2nd gateway option for testing so we don't impact our current users?&amp;nbsp; Basically, if users are connecting to vpn.contoso.com, we would create vpntest.contoso.com on the PA and use that to test this new configuration.&amp;nbsp;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;NOTE: I don't want to do pre-login or anything like that. And we don't have SAML as an option or AD Federated Services.&amp;nbsp; Just a very basic Active Directory 2016 domain, a single Palo Alto Firewall and GlobalProtect 5.1.5 for Windows 10.&amp;nbsp;&amp;nbsp;&lt;/P&gt;&lt;DIV class="ms-editor-squiggler"&gt;&amp;nbsp;&lt;/DIV&gt;</description>
    <pubDate>Wed, 03 Feb 2021 16:53:29 GMT</pubDate>
    <dc:creator>jrauman</dc:creator>
    <dc:date>2021-02-03T16:53:29Z</dc:date>
    <item>
      <title>Switching from GlobalProtect username &amp; password to some sort of SSO solution (on-prem AD only)</title>
      <link>https://live.paloaltonetworks.com/t5/globalprotect-discussions/switching-from-globalprotect-username-amp-password-to-some-sort/m-p/383670#M878</link>
      <description>&lt;P&gt;We have always used username &amp;amp; password for authenticating GlobalProtect (using the user's AD account/password). We always connect GlobalProtect AFTER signing on to Windows first.&amp;nbsp; So how difficult would it be to have GlobalProtect simply query Windows for the user's current signed-on creds to use instead of manually typing them? Essentially something like SSO?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;And is it possible to setup a 2nd gateway option for testing so we don't impact our current users?&amp;nbsp; Basically, if users are connecting to vpn.contoso.com, we would create vpntest.contoso.com on the PA and use that to test this new configuration.&amp;nbsp;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;NOTE: I don't want to do pre-login or anything like that. And we don't have SAML as an option or AD Federated Services.&amp;nbsp; Just a very basic Active Directory 2016 domain, a single Palo Alto Firewall and GlobalProtect 5.1.5 for Windows 10.&amp;nbsp;&amp;nbsp;&lt;/P&gt;&lt;DIV class="ms-editor-squiggler"&gt;&amp;nbsp;&lt;/DIV&gt;</description>
      <pubDate>Wed, 03 Feb 2021 16:53:29 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/globalprotect-discussions/switching-from-globalprotect-username-amp-password-to-some-sort/m-p/383670#M878</guid>
      <dc:creator>jrauman</dc:creator>
      <dc:date>2021-02-03T16:53:29Z</dc:date>
    </item>
  </channel>
</rss>

