Search code examples
ldapopendj

managing user data for multiple applications - opendj ldap


what is the best way to manage user data for multiple applications using opendj. is creating different backends with different baseDN a good option?

ex: 
backend1 baseDN dc=app1,dc=abc,dc=company,dc=com
backend2 baseDN dc=app2,dc=abc,dc=company,dc=com
....

searching in this case be done using,

  $ ldapsearch --baseDN dc=app1,dc=abc,dc=company,dc=com "search"

or modify the modify the ldap schema to include an objectClass/attribute value as an application name? in this case, searching certainly can be an issue.


Solution

  • It really depends what you are trying to achieve. Usually, it is preferable to have a user be represented by a single entry (and single credentials for the user). The application specific data can be either a set of attributes (from an Auxiliary objectClass) or a set of sub entries.

    But if the application data is not user specific, and there are no (and very close to zero) duplicated data, the model of having a branch per application can work.