[Date Prev][Date Next] [Chronological] [Thread] [Top]

Newbie: Design Issues

  We want to build a ldap directory structure that
accomodates our application requirements. Given below
is an analogy of the problem we want to resolve
   Suppose an application A has attributes userid,
password, required1, required2 amd application B has
attributes userid, password, required3, required4. A
user may have access to one or both applications. How
do we design the LDAP directory structure to
accomodate the described scenario.
  One of the ways that can be done is to have a
separte directory for each application and add the
user entry in each one of them. But is it possible to
have a single directory where we could add user
entries that somehow specify that 
i) the user has access to the various applications.
ii) Only provide values for the applications that
he/she has access. For example, if John Doe has access
to application A but not for application B, then John
Doe needs to have attributes for required1 and
required2 but not for required3 & required4. To be
more specific, we do not want to add all the
attributes possible for all the appliations and then
blank out the values of the attributes that do not
correspond to the user. Is there a way to get only the
attributes that are accessed by the application.

   Sorry if I have confused you but any suggestions
would be helpful. Thanks for your help.


Do You Yahoo!?
Send FREE video emails in Yahoo! Mail!