Difference between revisions of "stoney core: People Resource Mapping (REST - LDAP)"
From stoney cloud
| [unchecked revision] | [unchecked revision] |
(Created page with "= Overview = The people resource mapping describes the business logic behind the LDAP to JSON transformation and visa versa for the request and response objects. The actual pe...") |
|||
| Line 6: | Line 6: | ||
* for collections only a subset of the resource object attributes will be returned which may be also be merged or otherwise mangled | * for collections only a subset of the resource object attributes will be returned which may be also be merged or otherwise mangled | ||
| − | This specification puts together the [[stoney core: People Resource - REST API| | + | This specification puts together the [[stoney core: People Resource - REST API|People frontend API]] (stoney core: People Resource - REST API) and the [[stoney core: OpenLDAP directory data organisation|LDAP Data Backend]] (stoney core: OpenLDAP directory data organisation). |
[[Category:Mapping (REST - LDAP)]] | [[Category:Mapping (REST - LDAP)]] | ||
Latest revision as of 11:49, 21 February 2014
Overview
The people resource mapping describes the business logic behind the LDAP to JSON transformation and visa versa for the request and response objects. The actual people resource REST API is located in the REST API category and is named stoney core: People Resource - REST API.
Principles:
- for the resource 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 resource object attributes will be returned which may be also be merged or otherwise mangled
This specification puts together the People frontend API (stoney core: People Resource - REST API) and the LDAP Data Backend (stoney core: OpenLDAP directory data organisation).
