<?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: Global Protect Pre-Logon followed by SAML SSO in GlobalProtect Discussions</title>
    <link>https://live.paloaltonetworks.com/t5/globalprotect-discussions/global-protect-pre-logon-followed-by-saml-sso/m-p/347691#M400</link>
    <description>&lt;P&gt;I'm not sure if this applies in your case, but I saw something similar when a user had two client certificates which matched the certificate profile. We solved it by deleting one of the unneeded certificates.&lt;/P&gt;</description>
    <pubDate>Tue, 08 Sep 2020 21:17:31 GMT</pubDate>
    <dc:creator>OwenFuller</dc:creator>
    <dc:date>2020-09-08T21:17:31Z</dc:date>
    <item>
      <title>Global Protect Pre-Logon followed by SAML SSO</title>
      <link>https://live.paloaltonetworks.com/t5/globalprotect-discussions/global-protect-pre-logon-followed-by-saml-sso/m-p/347378#M395</link>
      <description>&lt;P&gt;Hi Guys,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I have implemented global protect with pre-logon (device certificate) followed by user logon using SAML (Azure AD as SAML IDP)&lt;/P&gt;&lt;P&gt;When global protect client initiate the user authentication below windows security pop up asking to confirm the certificate.&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="NamalW_0-1599546178555.png" style="width: 400px;"&gt;&lt;img src="https://live.paloaltonetworks.com/t5/image/serverpage/image-id/27646iAB22B97FD1816237/image-size/medium/is-moderation-mode/true?v=v2&amp;amp;px=400" role="button" title="NamalW_0-1599546178555.png" alt="NamalW_0-1599546178555.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;After confirming the certificate it connects fine and every time user reboot same pop up box comes up, if I replace the SAML auth with LDAP auth, I don't get any pops for certificate and everything works fine.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I have client certificate profile (internal Root and Intermediate CA) attached to client profile in each scenario ( LDAP auth vs SAML)&lt;/P&gt;&lt;P&gt;Also note that pre-logon works fine on each scenario and I can see before login to the machine globalprotect shows connected.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Has anyone come across this or similar issue?&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;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 08 Sep 2020 06:30:00 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/globalprotect-discussions/global-protect-pre-logon-followed-by-saml-sso/m-p/347378#M395</guid>
      <dc:creator>Namalw</dc:creator>
      <dc:date>2020-09-08T06:30:00Z</dc:date>
    </item>
    <item>
      <title>Re: Global Protect Pre-Logon followed by SAML SSO</title>
      <link>https://live.paloaltonetworks.com/t5/globalprotect-discussions/global-protect-pre-logon-followed-by-saml-sso/m-p/347691#M400</link>
      <description>&lt;P&gt;I'm not sure if this applies in your case, but I saw something similar when a user had two client certificates which matched the certificate profile. We solved it by deleting one of the unneeded certificates.&lt;/P&gt;</description>
      <pubDate>Tue, 08 Sep 2020 21:17:31 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/globalprotect-discussions/global-protect-pre-logon-followed-by-saml-sso/m-p/347691#M400</guid>
      <dc:creator>OwenFuller</dc:creator>
      <dc:date>2020-09-08T21:17:31Z</dc:date>
    </item>
    <item>
      <title>Re: Global Protect Pre-Logon followed by SAML SSO</title>
      <link>https://live.paloaltonetworks.com/t5/globalprotect-discussions/global-protect-pre-logon-followed-by-saml-sso/m-p/349645#M411</link>
      <description>&lt;P&gt;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/63582"&gt;@Namalw&lt;/a&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I have seen this similar behaviour in our setup.&lt;/P&gt;
&lt;P&gt;We also have GP pre logon with machine cert and then SAML Azure authentication.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;That cert pop message is for&amp;nbsp;&lt;SPAN&gt;&amp;nbsp;the certificate to sign SAML messages to IDP and we select that in Authentication profile.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;Regards&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 16 Sep 2020 04:55:04 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/globalprotect-discussions/global-protect-pre-logon-followed-by-saml-sso/m-p/349645#M411</guid>
      <dc:creator>MP18</dc:creator>
      <dc:date>2020-09-16T04:55:04Z</dc:date>
    </item>
    <item>
      <title>Re: Global Protect Pre-Logon followed by SAML SSO</title>
      <link>https://live.paloaltonetworks.com/t5/globalprotect-discussions/global-protect-pre-logon-followed-by-saml-sso/m-p/349660#M412</link>
      <description>&lt;P&gt;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/75039"&gt;@MP18&lt;/a&gt;&amp;nbsp; Is there any workaround to fix it? This is not convenient for users&lt;/P&gt;</description>
      <pubDate>Wed, 16 Sep 2020 05:02:18 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/globalprotect-discussions/global-protect-pre-logon-followed-by-saml-sso/m-p/349660#M412</guid>
      <dc:creator>Namalw</dc:creator>
      <dc:date>2020-09-16T05:02:18Z</dc:date>
    </item>
    <item>
      <title>Re: Global Protect Pre-Logon followed by SAML SSO</title>
      <link>https://live.paloaltonetworks.com/t5/globalprotect-discussions/global-protect-pre-logon-followed-by-saml-sso/m-p/350274#M421</link>
      <description>&lt;P&gt;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/63582"&gt;@Namalw&lt;/a&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Do you have&amp;nbsp; more than 1 certs issued by your Intermediate Certs.?&lt;/P&gt;
&lt;P&gt;either way you need to have SSL/TLS profile cert trusted by&amp;nbsp; either your Internal PKI or external certificate authority.&lt;/P&gt;
&lt;P&gt;It needs same CA cert signed by the above one which your PC also trusts.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Regards&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 18 Sep 2020 02:15:21 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/globalprotect-discussions/global-protect-pre-logon-followed-by-saml-sso/m-p/350274#M421</guid>
      <dc:creator>MP18</dc:creator>
      <dc:date>2020-09-18T02:15:21Z</dc:date>
    </item>
    <item>
      <title>Re: Global Protect Pre-Logon followed by SAML SSO</title>
      <link>https://live.paloaltonetworks.com/t5/globalprotect-discussions/global-protect-pre-logon-followed-by-saml-sso/m-p/376137#M744</link>
      <description>&lt;P&gt;To stop the client certificate pop-up you need to make sure the VPN&amp;nbsp; url is either in your local intranet zone or in your trusted sites with IE Options configured "d&lt;EM&gt;on't prompt&lt;/EM&gt;&lt;SPAN&gt;&amp;nbsp;for&amp;nbsp;&lt;/SPAN&gt;&lt;EM&gt;client certificate&lt;/EM&gt;&lt;SPAN&gt;&amp;nbsp;selection when no certificates or only one certificate exists " which needs to be set to enable&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;For Chrome and Edge the policy&amp;nbsp;AutoSelectCertificateForUrls&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;A href="https://docs.microsoft.com/en-us/deployedge/microsoft-edge-policies#autoselectcertificateforurls" target="_blank"&gt;Microsoft Edge Browser Policy Documentation | Microsoft Docs&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;A href="https://cloud.google.com/docs/chrome-enterprise/policies/?policy=AutoSelectCertificateForUrls" target="_blank"&gt;Chrome Enterprise Policy List &amp;amp; Management &amp;nbsp;|&amp;nbsp; Documentation (google.com)&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 24 Dec 2020 17:34:37 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/globalprotect-discussions/global-protect-pre-logon-followed-by-saml-sso/m-p/376137#M744</guid>
      <dc:creator>rajjair</dc:creator>
      <dc:date>2020-12-24T17:34:37Z</dc:date>
    </item>
    <item>
      <title>Re: Global Protect Pre-Logon followed by SAML SSO</title>
      <link>https://live.paloaltonetworks.com/t5/globalprotect-discussions/global-protect-pre-logon-followed-by-saml-sso/m-p/377799#M757</link>
      <description>&lt;P&gt;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/63582"&gt;@Namalw&lt;/a&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Also you can push this registry setting with GP agent then cert pop up will not occur.&lt;/P&gt;
&lt;P&gt;Check this link&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;A href="https://docs.paloaltonetworks.com/pan-os/7-1/pan-os-new-features/globalprotect-features/certificate-selection-by-oid" target="_blank"&gt;Certificate Selection by OID (paloaltonetworks.com)&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Regards&lt;/P&gt;</description>
      <pubDate>Mon, 04 Jan 2021 22:12:25 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/globalprotect-discussions/global-protect-pre-logon-followed-by-saml-sso/m-p/377799#M757</guid>
      <dc:creator>MP18</dc:creator>
      <dc:date>2021-01-04T22:12:25Z</dc:date>
    </item>
    <item>
      <title>Re: Global Protect Pre-Logon followed by SAML SSO</title>
      <link>https://live.paloaltonetworks.com/t5/globalprotect-discussions/global-protect-pre-logon-followed-by-saml-sso/m-p/459560#M2337</link>
      <description>&lt;P&gt;Did you ever resolve this? Have messed around with different certificates but still getting the scenario you described. If you did solve it, any pointers would be useful.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 19 Jan 2022 15:35:51 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/globalprotect-discussions/global-protect-pre-logon-followed-by-saml-sso/m-p/459560#M2337</guid>
      <dc:creator>BryanWillsMOL</dc:creator>
      <dc:date>2022-01-19T15:35:51Z</dc:date>
    </item>
    <item>
      <title>Re: Global Protect Pre-Logon followed by SAML SSO</title>
      <link>https://live.paloaltonetworks.com/t5/globalprotect-discussions/global-protect-pre-logon-followed-by-saml-sso/m-p/582669#M5222</link>
      <description>&lt;P&gt;One additional thing to add here is a clarifying question and some details about how to work around one of the scenarios:&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;-Are you looking to use user certificates in any way/shape form?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;If not, one thing that's been suggested to use separate intermediate CAs for issuing user and machine certificates. When configuring the certificate profile, only configure the intermediate CA that signed the machine certificates and then the user certs won't match and therefore will keep the prompts suppressed.&amp;nbsp; Testing currently in progress for this. Will report back&lt;/P&gt;</description>
      <pubDate>Thu, 04 Apr 2024 16:25:16 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/globalprotect-discussions/global-protect-pre-logon-followed-by-saml-sso/m-p/582669#M5222</guid>
      <dc:creator>chmotley</dc:creator>
      <dc:date>2024-04-04T16:25:16Z</dc:date>
    </item>
  </channel>
</rss>

