Comments on: Documentum and LDAP, Time to Grow Up http://wordofpie.com/2009/05/05/documentum-and-ldap-time-to-grow-up/ Ponderings on Life, the Universe, and Information Fri, 25 May 2012 11:29:30 +0000 hourly 1 http://wordpress.com/ By: Rich Blank http://wordofpie.com/2009/05/05/documentum-and-ldap-time-to-grow-up/#comment-4963 Thu, 25 Jun 2009 03:57:41 +0000 http://wordofpie.wordpress.com/2009/05/05/documentum-and-ldap-time-to-grow-up/#comment-4963 completely agree. they should really take a look at eRoom and it’s ldap wizard. easy to add ldap connection and it just works….

]]> By: Pie http://wordofpie.com/2009/05/05/documentum-and-ldap-time-to-grow-up/#comment-3936 Wed, 06 May 2009 16:05:28 +0000 http://wordofpie.wordpress.com/2009/05/05/documentum-and-ldap-time-to-grow-up/#comment-3936 Responding to you once…Yes, you are correct, it does solve the problem. Why EMC Support never said this in over a week is a mystery to me. Making the change to the Authentication Protocol setting on the repository from “Domain required” to Domain not Required” necessitates the running of a script and is a one-way change that cannot be undone.

Support Note:
https://solutions.emc.com/emcsolutionview.asp?id=esg6339

Still doesn’t alleviate the issue with the user’s name needing to be unique.

Going to try it, but will have to back-up the Dev environment first because not being able to roll-back is a problem.

]]> By: Bongo http://wordofpie.com/2009/05/05/documentum-and-ldap-time-to-grow-up/#comment-3929 Wed, 06 May 2009 12:55:40 +0000 http://wordofpie.wordpress.com/2009/05/05/documentum-and-ldap-time-to-grow-up/#comment-3929 Entirely agree with you on this. Unfortunately, this is still one of the issues that plagues Documentum in many areas. It’s all over the RPS/RM models, where users are referenced by name not ID.

]]> By: ChaithanyaLekkalapudi http://wordofpie.com/2009/05/05/documentum-and-ldap-time-to-grow-up/#comment-3925 Wed, 06 May 2009 05:44:29 +0000 http://wordofpie.wordpress.com/2009/05/05/documentum-and-ldap-time-to-grow-up/#comment-3925 So configuring a docbase in domain required mode tries to solve this problem even in the case of LDAP.

]]> By: ChaithanyaLekkalapudi http://wordofpie.com/2009/05/05/documentum-and-ldap-time-to-grow-up/#comment-3924 Wed, 06 May 2009 05:22:47 +0000 http://wordofpie.wordpress.com/2009/05/05/documentum-and-ldap-time-to-grow-up/#comment-3924 Hi pie,

The following statement may not be true all the times”Due to old, legacy, design considerations, both the user’s login id and the user’s name must be unique in the entire repository”. It is only username which corresponds to user_name of dm_user object type required to be unique, we can create two user object’s with the same user login id(user_login_name) with a different user login domain when the domain required mode is turned on the docbase. So the user login id need not be unique in case of multi domain environment and when the domain required mode is turned on.In case of LDAP config, the LDAP config object name becomes the user login domain for the users that have been synchronized from the corresponding LDAP server and you can point one LDAP config object to only one LDAP server(If we have two domains, we can create a seperate LDAP config object for each and every domain), so two users with the same login id but from different directory server can coexist with the restriction that user name is not same and domain needs to be provided while corresponding user’s login.

]]>