<?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 Jabber with Multi-Forest/Domain and SSO in Collaboration Applications</title>
    <link>https://community.cisco.com/t5/collaboration-applications/jabber-with-multi-forest-domain-and-sso/m-p/3927680#M40991</link>
    <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;We are planning a new deployment for a client with multiple forests and domains. I know that you can use LDS to combine the directories and allow users to login. If we were to implement SSO and the IdP was able to authenticate users in each domain, would we need to do LDS still? I know we would need to do the LDAP directory sync but I'm wondering if SSO would negate having to do the LDAP authentication in CUCM.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thank you,&lt;/P&gt;&lt;P&gt;James&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Fri, 20 Sep 2019 15:34:56 GMT</pubDate>
    <dc:creator>jriacono5</dc:creator>
    <dc:date>2019-09-20T15:34:56Z</dc:date>
    <item>
      <title>Jabber with Multi-Forest/Domain and SSO</title>
      <link>https://community.cisco.com/t5/collaboration-applications/jabber-with-multi-forest-domain-and-sso/m-p/3927680#M40991</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;We are planning a new deployment for a client with multiple forests and domains. I know that you can use LDS to combine the directories and allow users to login. If we were to implement SSO and the IdP was able to authenticate users in each domain, would we need to do LDS still? I know we would need to do the LDAP directory sync but I'm wondering if SSO would negate having to do the LDAP authentication in CUCM.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thank you,&lt;/P&gt;&lt;P&gt;James&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 20 Sep 2019 15:34:56 GMT</pubDate>
      <guid>https://community.cisco.com/t5/collaboration-applications/jabber-with-multi-forest-domain-and-sso/m-p/3927680#M40991</guid>
      <dc:creator>jriacono5</dc:creator>
      <dc:date>2019-09-20T15:34:56Z</dc:date>
    </item>
    <item>
      <title>Re: Jabber with Multi-Forest/Domain and SSO</title>
      <link>https://community.cisco.com/t5/collaboration-applications/jabber-with-multi-forest-domain-and-sso/m-p/3927969#M41002</link>
      <description>SSO does not negate the LDAP sync - you still need to pull End Users in to the database.&lt;BR /&gt;&lt;BR /&gt;The only officially supported way to support multi-forest on the same cluster is with MS LDS. The problem is that LDS is very poorly understood by most Microsoft admins. You may want to consider the viability of a cluster per-forest and rely on things such as ILS, EMCC, IM&amp;amp;P Inter-Cluster Peering, and CUC HTTPS Digital Networking instead.</description>
      <pubDate>Sat, 21 Sep 2019 15:04:25 GMT</pubDate>
      <guid>https://community.cisco.com/t5/collaboration-applications/jabber-with-multi-forest-domain-and-sso/m-p/3927969#M41002</guid>
      <dc:creator>Jonathan Schulenberg</dc:creator>
      <dc:date>2019-09-21T15:04:25Z</dc:date>
    </item>
  </channel>
</rss>

