Configure common directory services for the security configuration

Overview

IBM Connections portlets use the common directory services to enable directory lookup from IBM Connections in the IBM WebSphere Portal environment. This enables type-ahead for finding names. Common directory services are enabled and configured automatically as part of the installation process.

To use common directory services, Portal must be configured to use a federated LDAP. Use of a stand-alone LDAP is not supported.

Configure common directory services for the Connections portlets

1. Copy the configuration files:
   • directory.services.xml
   • directory.services.xsd
   • sonata.services.xml
   • sonata.services.xsd

   ...from...

   WP_PROFILE/paa/SNPortlets/components/SNPortlets/config/templates/deployment

   ...to either...

   Standalone PORTAL_HOME/wp_profile/config/cells/cell Cluster DMGR_PROFILE/config/cells/cell

   For SiteMinder and SPNEGO configuration, the Communities and Profiles services URLs in directory-services.xml should point to the interServiceURL as below: For a Siteminder and SPNEGO configuration, the Communities and Profiles services URLs in directory-services.xml should point to the interServiceURL. For example,

   <!-- *** WPI can only be used when Profiles services is available *** -->
   <property name="com.ibm.connections.directory.services.waltz.profiles.integration.service.url">
       <interServiceURL>/profiles/dsx/</interServiceURL>
   </property>
   
   <!-- *** WCI can only be used when Waltz is running on SSO enabled environment *** -->
   <property name="com.ibm.connections.directory.services.waltz.communities.integration.service.url">
       <interServiceURL>/communities/dsx/</interServiceURL>
   </property>
   

2. If we are using LTPA SSO, skip this procedure because no change is required. For other types of authentication, edit sonata.services.xml, and change the sonataServices tag...
   <sonataServices name="DefaultAuthenticator">

   ...to the appropriate value for the name attribute.

   SPNEGO	<sonataServices name="KerberosAuthenticator">
   Tivoli Access Manager	<sonataServices name="TAMAuthenticator">
   SiteMinder	<sonataServices name="SiteMinderAuthenticator">
   Tivoli Access Manager and SPNEGO	<sonataServices name="KerberosAuthenticator"> On a Portal 8 server, use <sonataServices name="TAMAuthenticator">
   SiteMinder and SPNEGO	<sonataServices name="DefaultAuthenticator">

3. Re-sync with nodes...
   System Administration | Nodes | WebSphere Portal nodes | Full Resynchronize

4. Restart the Portal server after you update...
   directory.services.xml

   ...or restart all of the servers for a clustered deployment.

Parent topic:
Deploy the Connections Portlets

Related:

Use the Profiles database as the user directory