Once Rest2Ldap supports inheritance and sub-resources it should be possible to provide REST access to OpenDJ's configuration and monitoring backends.
- cn=monitor is schema-less so the JSON mapping will be a little sub-optimal. For example, all attributes will be exposed as multi-valued strings
- cn=config's Rest2Ldap configuration can be derived at run-time from the configuration framework.
Out of scope for now:
- schema backend - this should be straightforward, although I'd prefer to wait for feedback on the config/monitoring endpoints before proceeding any further
- task backend - we could expose this directly, or as actions against the associated components in the config. For example, a JE backend may expose actions for rebuilding indexes.