<?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: Kerberos Transparent Auth with multiple domains and server 2012 in Firewall and Security Management</title>
    <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Kerberos-Transparent-Auth-with-multiple-domains-and-server-2012/m-p/83477#M11402</link>
    <description>&lt;P&gt;Yes when you add the SPN -a it used to bypass the check on duplicate entries in the forest. In Server 2012 this has been changed it checks for duplicates anyway.&lt;/P&gt;&lt;P&gt;This same SPN needs to be added in each domain for SSO to work.&amp;nbsp;&lt;/P&gt;&lt;P&gt;So yes the issue is that the same SPN's are used in each domain.&lt;/P&gt;&lt;P&gt;Works ok now - as the SPN's are already there.&lt;/P&gt;&lt;P&gt;However when we get a new firewall with a new name in a different location - we will have a problem for Kerberos SSO as it stands.&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, 28 Apr 2020 11:34:26 GMT</pubDate>
    <dc:creator>Simon_Croston</dc:creator>
    <dc:date>2020-04-28T11:34:26Z</dc:date>
    <item>
      <title>Kerberos Transparent Auth with multiple domains and server 2012</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Kerberos-Transparent-Auth-with-multiple-domains-and-server-2012/m-p/83084#M11400</link>
      <description>&lt;P&gt;For a number of years we have been happily using Kerberos Transparent Auth SSO. We have multiple domains around the world.&lt;/P&gt;&lt;P&gt;This continues to work fine for existing gateways. We use the identity agent and with browser based sso as a backup.&lt;/P&gt;&lt;P&gt;So each domain would have the SPN for the gateway and the&amp;nbsp;ckp_pdp registered. Has worked fine - for years.&lt;/P&gt;&lt;P&gt;The problem we have regards new gateways that we want to have registered in AD. Previously in a server 2008 AD environment you could have duplicate SPN's in a forest - ie so each domain can have the new firewall registered.&lt;/P&gt;&lt;P&gt;On server 2012 AD controllers the use of SPN -a has been depreciated and the SPN has to be unique in the forest. This means that we cannot register the new gateway in each domain.&lt;/P&gt;&lt;P&gt;Has anyone else encountered this - we want to stick with the identity agent, and no identity collectors or AD query.&lt;/P&gt;&lt;P&gt;How did you address this situation. It has only recently been an issue as we have a couple of new gateways and the last of the old 2008 AD controllers have now gone.&lt;/P&gt;&lt;P&gt;Thanks&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>Fri, 24 Apr 2020 15:37:33 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Kerberos-Transparent-Auth-with-multiple-domains-and-server-2012/m-p/83084#M11400</guid>
      <dc:creator>Simon_Croston</dc:creator>
      <dc:date>2020-04-24T15:37:33Z</dc:date>
    </item>
    <item>
      <title>Re: Kerberos Transparent Auth with multiple domains and server 2012</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Kerberos-Transparent-Auth-with-multiple-domains-and-server-2012/m-p/83406#M11401</link>
      <description>&lt;P&gt;Is the fact the same SPN is used with both domains the issue?&lt;BR /&gt;Tagging&amp;nbsp;&lt;a href="https://community.checkpoint.com/t5/user/viewprofilepage/user-id/8232"&gt;@Royi_Priov&lt;/a&gt;.&lt;/P&gt;</description>
      <pubDate>Tue, 28 Apr 2020 01:11:34 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Kerberos-Transparent-Auth-with-multiple-domains-and-server-2012/m-p/83406#M11401</guid>
      <dc:creator>PhoneBoy</dc:creator>
      <dc:date>2020-04-28T01:11:34Z</dc:date>
    </item>
    <item>
      <title>Re: Kerberos Transparent Auth with multiple domains and server 2012</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Kerberos-Transparent-Auth-with-multiple-domains-and-server-2012/m-p/83477#M11402</link>
      <description>&lt;P&gt;Yes when you add the SPN -a it used to bypass the check on duplicate entries in the forest. In Server 2012 this has been changed it checks for duplicates anyway.&lt;/P&gt;&lt;P&gt;This same SPN needs to be added in each domain for SSO to work.&amp;nbsp;&lt;/P&gt;&lt;P&gt;So yes the issue is that the same SPN's are used in each domain.&lt;/P&gt;&lt;P&gt;Works ok now - as the SPN's are already there.&lt;/P&gt;&lt;P&gt;However when we get a new firewall with a new name in a different location - we will have a problem for Kerberos SSO as it stands.&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, 28 Apr 2020 11:34:26 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Kerberos-Transparent-Auth-with-multiple-domains-and-server-2012/m-p/83477#M11402</guid>
      <dc:creator>Simon_Croston</dc:creator>
      <dc:date>2020-04-28T11:34:26Z</dc:date>
    </item>
    <item>
      <title>Re: Kerberos Transparent Auth with multiple domains and server 2012</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Kerberos-Transparent-Auth-with-multiple-domains-and-server-2012/m-p/84074#M11403</link>
      <description>&lt;P&gt;Any update on this?&lt;/P&gt;</description>
      <pubDate>Mon, 04 May 2020 12:53:47 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Kerberos-Transparent-Auth-with-multiple-domains-and-server-2012/m-p/84074#M11403</guid>
      <dc:creator>Simon_Croston</dc:creator>
      <dc:date>2020-05-04T12:53:47Z</dc:date>
    </item>
  </channel>
</rss>

