Difference between revisions of "stoney core: Resellers Resource Mapping (REST - LDAP)"
From stoney cloud
| [unchecked revision] | [unchecked revision] |
(the mapping is not per-se tied to a method) |
(→Overview) |
||
| Line 5: | Line 5: | ||
* for the ressource objects there is most of the time a one-to-one mapping between LDAP attributes and JSON object | * for the ressource objects there is most of the time a one-to-one mapping between LDAP attributes and JSON object | ||
* for collections only a subset of the ressource object attributes will be returned which may be also be merged or otherwise mangled | * for collections only a subset of the ressource object attributes will be returned which may be also be merged or otherwise mangled | ||
| + | |||
| + | This specification puts together the [[stoney core: Resellers Resource - REST API|Reseller frontend API]] and the [[stoney core: OpenLDAP directory data organisation|LDAP Data Backend]] | ||
= Resellers Resource Mapping = | = Resellers Resource Mapping = | ||
Revision as of 17:58, 3 January 2014
Overview
The resellers resource mapping describes the business logic behind the LDAP to JSON transformation and visa versa for the request and response objects. The actual resellers resource REST API is located in the REST API category and is named stoney core: Resellers Resource - REST API.
Principles:
- for the ressource objects there is most of the time a one-to-one mapping between LDAP attributes and JSON object
- for collections only a subset of the ressource object attributes will be returned which may be also be merged or otherwise mangled
This specification puts together the Reseller frontend API and the LDAP Data Backend
