We need to be able to support recursive child-containers which are resolved dynamically during routing. Do we want explicit support for this, or simply rely on users creating sub-routers and dynamically creating LDAP containers on the fly?
Here's some additional use cases taken from OPENDJSDK-70: multi-tenant and deep hierarchical layout of resources in LDAP:
- multi-tenant support using simple naming (e.g. tenant = "example")
- URI pattern: /{tenant}/users/{id}
- DN pattern: uid={id},ou=people,dc={tenant},dc=com
- multi-tenant support using regex naming (e.g. tenant = "example.com")
- URI pattern: /{tenant}/users/{id}
- Regex pattern: ([^.]+)\.([^.]+)
- DN pattern: uid={id},ou=people,dc=$1,dc=$2
- deep hierarchy:
dc=com,dc=example | +---ou=org1 | +---uid=user1A | +---uid=user1B | +---... | +---ou=org2 | +---uid=user2A | +---uid=user2B | +---... | +---...
Where you want a single HTTP end-point /users for all users regardless of their organizational unit. The assumption is that the associated JSON resources would contain a field indicating the OU to which the resource belongs. This would allow create (POST) requests to work since the parent DN cannot be determined without this information.
- is duplicated by
-
OPENDJ-2879 Rest2LDAP: support multi-tenancy and deep hierarchical layout of resources in LDAP
-
- Done
-
- is related to
-
OPENDJ-2888 Implement a dynamic routing and mapping mode for Rest2LDAP
-
- Dev backlog
-
-
OPENDJ-2774 Define revised Rest2LDAP configuration model
-
- Done
-
-
OPENDJ-863 Add support for deleting collection
-
- Dev backlog
-
- is required by
-
OPENDJ-3050 Document REST2LDAP support for inheritance, sub-resources, and other fixes
-
- Done
-
- relates to
-
OPENDJ-5008 RFE: rest2ldap to allow subtree searches
-
- Dev backlog
-