Recommend user search: LDAP vs Local
Hi all!
My customer always stay in doubt about search users. Since which the search user screen shows a checkbox to force the search on LDAP, he has doubts about what is the better way (or recommended) to search an user. His LDAP is a bit slow, so for him it's more confortable to do search on local user tables, but there's any implication on it? |
One answer
Hi,
The difference is that a local search only finds users who are already registered with RAM. If they wanted someone not registered yet they wouldn't find them. Generally LDAP is faster, though we search on less fields and a more constrained search. Local will probably result in a complete scan of the user list in the database. but for most installations this list is not that big and would probably be fast. Databases, such as DB2, are actually quite good at scanning large volumes of data. -- Rich Kulp Rational Asset Manager developer Comments
Pramod Chavan
commented Oct 31 '13, 5:25 a.m.
Rich,
Can we configure RAM to ALWAYS search users from LDAP?
I am facing an issue, when I import a library with assets. These assets have user-selection attribute(author attribute). As most of the users are not registered in RAM instead of their names, their id is displayed.
Regards,
Pramod
|
Your answer
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.