<?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: GP SSO SAML Azure AD - Microsoft SSO Login Page in GlobalProtect Discussions</title>
    <link>https://live.paloaltonetworks.com/t5/globalprotect-discussions/gp-sso-saml-azure-ad-microsoft-sso-login-page/m-p/334229#M219</link>
    <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;PanOS supports SP initiated authentication for SAML, so when the user authenticates to the idP, the client will hold an SSO cookie, to authenticate all subsequent connections, hence SSO will work. But if the Cookie expires from the idP side and/or login lifetime has expired on the firewall, then the user will be initiated to authenticate again.&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;You can extend the login time from your idP side, as well as the firewall Login Lifetime on the gateway side. If both of these are extended, then the user should be able to authenticate for a longer period of time, but they will still be prompted to authenticate once the SSO session expires.&amp;nbsp; Currently, the GP client uses an embedded browser like IE for windows, and it can't use the SSO session from let's say Chrome browser, where the user might have already authenticated to the idp.&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;Starting GP client 5.2, you will have the option to set a default browser for the user i.e. Chrome and it should allow GP client to use SSO session if the user has already authenticated to the idp.&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;Let me know if that helps!&lt;BR /&gt;&lt;BR /&gt;Thanks and stay safe&lt;/P&gt;</description>
    <pubDate>Fri, 19 Jun 2020 00:22:08 GMT</pubDate>
    <dc:creator>khans</dc:creator>
    <dc:date>2020-06-19T00:22:08Z</dc:date>
    <item>
      <title>GP SSO SAML Azure AD - Microsoft SSO Login Page</title>
      <link>https://live.paloaltonetworks.com/t5/globalprotect-discussions/gp-sso-saml-azure-ad-microsoft-sso-login-page/m-p/334142#M214</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Why sometime we see the Microsoft SSO Login page requesting password ?&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Most of the time, this is seemless and transparent to user, and we do not have to enter username/password which show me that SSO is working great. However, like I said, sometime, we got the&amp;nbsp;Microsoft SSO Login page requesting password.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I'm just wondering which cause the Microsoft Login page to request entering password during logon.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 18 Jun 2020 17:42:42 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/globalprotect-discussions/gp-sso-saml-azure-ad-microsoft-sso-login-page/m-p/334142#M214</guid>
      <dc:creator>Dominic_Longpre</dc:creator>
      <dc:date>2020-06-18T17:42:42Z</dc:date>
    </item>
    <item>
      <title>Re: GP SSO SAML Azure AD - Microsoft SSO Login Page</title>
      <link>https://live.paloaltonetworks.com/t5/globalprotect-discussions/gp-sso-saml-azure-ad-microsoft-sso-login-page/m-p/334229#M219</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;PanOS supports SP initiated authentication for SAML, so when the user authenticates to the idP, the client will hold an SSO cookie, to authenticate all subsequent connections, hence SSO will work. But if the Cookie expires from the idP side and/or login lifetime has expired on the firewall, then the user will be initiated to authenticate again.&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;You can extend the login time from your idP side, as well as the firewall Login Lifetime on the gateway side. If both of these are extended, then the user should be able to authenticate for a longer period of time, but they will still be prompted to authenticate once the SSO session expires.&amp;nbsp; Currently, the GP client uses an embedded browser like IE for windows, and it can't use the SSO session from let's say Chrome browser, where the user might have already authenticated to the idp.&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;Starting GP client 5.2, you will have the option to set a default browser for the user i.e. Chrome and it should allow GP client to use SSO session if the user has already authenticated to the idp.&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;Let me know if that helps!&lt;BR /&gt;&lt;BR /&gt;Thanks and stay safe&lt;/P&gt;</description>
      <pubDate>Fri, 19 Jun 2020 00:22:08 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/globalprotect-discussions/gp-sso-saml-azure-ad-microsoft-sso-login-page/m-p/334229#M219</guid>
      <dc:creator>khans</dc:creator>
      <dc:date>2020-06-19T00:22:08Z</dc:date>
    </item>
  </channel>
</rss>

