<?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: User kerberos athentification for MUHv2 agent in Firewall and Security Management</title>
    <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/User-kerberos-athentification-for-MUHv2-agent/m-p/168324#M30448</link>
    <description>&lt;P&gt;I know, my identity agents use kerberos for users and machines. But terminal agent on windows servers use for users (trust). My question: Its possible to change authentification for users or why terminal agent use trust instead of kerberos ? Both agent have same configuration on GW.&lt;/P&gt;</description>
    <pubDate>Thu, 19 Jan 2023 09:23:54 GMT</pubDate>
    <dc:creator>vonsakfilip</dc:creator>
    <dc:date>2023-01-19T09:23:54Z</dc:date>
    <item>
      <title>User kerberos athentification for MUHv2 agent</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/User-kerberos-athentification-for-MUHv2-agent/m-p/168312#M30446</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;Its possible to configure kerberos authentification for users on terminal agent MUHv2 ? Machine authetification works but users use authentification trust. Thanks.&lt;/P&gt;</description>
      <pubDate>Thu, 19 Jan 2023 08:38:12 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/User-kerberos-athentification-for-MUHv2-agent/m-p/168312#M30446</guid>
      <dc:creator>vonsakfilip</dc:creator>
      <dc:date>2023-01-19T08:38:12Z</dc:date>
    </item>
    <item>
      <title>Re: User kerberos athentification for MUHv2 agent</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/User-kerberos-athentification-for-MUHv2-agent/m-p/168315#M30447</link>
      <description>&lt;P&gt;According to&amp;nbsp;&lt;SPAN&gt;sk66761, kerberos is one of the option. For more info, look into the documentation:&amp;nbsp;&lt;A href="https://sc1.checkpoint.com/documents/Identity_Awareness_Clients_Admin_Guide/Content/Search.htm?q=kerberos" target="_blank"&gt;https://sc1.checkpoint.com/documents/Identity_Awareness_Clients_Admin_Guide/Content/Search.htm?q=kerberos&lt;/A&gt;&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 19 Jan 2023 08:49:36 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/User-kerberos-athentification-for-MUHv2-agent/m-p/168315#M30447</guid>
      <dc:creator>_Val_</dc:creator>
      <dc:date>2023-01-19T08:49:36Z</dc:date>
    </item>
    <item>
      <title>Re: User kerberos athentification for MUHv2 agent</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/User-kerberos-athentification-for-MUHv2-agent/m-p/168324#M30448</link>
      <description>&lt;P&gt;I know, my identity agents use kerberos for users and machines. But terminal agent on windows servers use for users (trust). My question: Its possible to change authentification for users or why terminal agent use trust instead of kerberos ? Both agent have same configuration on GW.&lt;/P&gt;</description>
      <pubDate>Thu, 19 Jan 2023 09:23:54 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/User-kerberos-athentification-for-MUHv2-agent/m-p/168324#M30448</guid>
      <dc:creator>vonsakfilip</dc:creator>
      <dc:date>2023-01-19T09:23:54Z</dc:date>
    </item>
    <item>
      <title>Re: User kerberos athentification for MUHv2 agent</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/User-kerberos-athentification-for-MUHv2-agent/m-p/168331#M30449</link>
      <description>&lt;P&gt;&lt;SPAN&gt;sk164998:&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;H4&gt;&lt;A class="checkpoint_toggle" target="_blank"&gt;The Endpoint Identity Agent does not require a "Shared Secret". Why is this required for the TS Identity Agent?&lt;/A&gt;&lt;/H4&gt;
&lt;DIV id="Q128"&gt;
&lt;BLOCKQUOTE&gt;The Endpoint Identity Agent authenticates to the Identity Server either with a username and password or via a Kerberos Ticket. For the TS Identity Agent, the authentication of users is not issued the same way, and thus for the Identity Server to trust the other end, a shared secret is used. This is to remove the possibility that a user may use this ability to claim that he is running a Terminal Server and indicate a false user.
&lt;P class="1674126020908"&gt;&amp;nbsp;&lt;/P&gt;
&lt;/BLOCKQUOTE&gt;
&lt;/DIV&gt;</description>
      <pubDate>Thu, 19 Jan 2023 11:00:29 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/User-kerberos-athentification-for-MUHv2-agent/m-p/168331#M30449</guid>
      <dc:creator>_Val_</dc:creator>
      <dc:date>2023-01-19T11:00:29Z</dc:date>
    </item>
    <item>
      <title>Re: User kerberos athentification for MUHv2 agent</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/User-kerberos-athentification-for-MUHv2-agent/m-p/168337#M30450</link>
      <description>&lt;P&gt;Thanks&lt;/P&gt;</description>
      <pubDate>Thu, 19 Jan 2023 11:30:51 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/User-kerberos-athentification-for-MUHv2-agent/m-p/168337#M30450</guid>
      <dc:creator>vonsakfilip</dc:creator>
      <dc:date>2023-01-19T11:30:51Z</dc:date>
    </item>
  </channel>
</rss>

