IBM – Configuration Web Content Management for accomodating multiple LDAP sources


Problem

Each time syndication takes place between your IBM® Web Content Management (WCM) authoring and rendering nodes–each configured to access a different LDAP source–you have the run the MemberFixer tool to remove extraneous references and avoid "member not found" exceptions.

Symptom

The WCM users who author content are present in the internal user LDAP source. When syndication propagates content from the authoring to the rendering server, which is coupled to a different LDAP source, all the references to internal LDAP entries results in "member not found" exceptions.

The only known solution to remove those unnecessary references to is utilize the MemberFixer utility each time syndication runs.

Environment

Your IBM Web Content Management environment includes and authoring WCM server connected to one LDAP source and one or more WCM rendering services configured to perform user look-ups on a different LDAP source.

Resolving the problem

Running the MemberFixer after every syndication is not how the product is designed to function, nor is it a recommended solution.

Web Content Management integrates within environments possessing more than one LDAP environment so long as both the DN and WMM External ID for each member (internal as well as external) resolves to the correct entity in each of the various LDAP sources.

via IBM – Configuration Web Content Management for accomodating multiple LDAP sources

IBM – Configuring SSO between WebSphere Portal and Lotus Sametime when each use a different user directory


How do you configure an environment for Single Sign-on (SSO) when IBM® WebSphere® Portal authenticates against one Lightweight Directory Access Protocol (LDAP) directory (IBM Directory Server, in our example here) and Lotus® Sametime® authenticates against Native IBM Lotus Domino®?

via IBM – Configuring SSO between WebSphere Portal and Lotus Sametime when each use a different user directory.