Difference between revisions of "stoney core: Customers Resource Mapping (REST - LDAP)"
From stoney cloud
| [unchecked revision] | [unchecked revision] |
(Created page with "= Overview = The customers resource mapping describes the business logic behind the LDAP to JSON transformation and visa versa for the request and response objects. The actual...") |
(→Overview) |
||
| Line 7: | Line 7: | ||
This specification puts together the [[stoney core: Customers Resource - REST API|Customers frontend API]] (stoney core: Customers Resource - REST API) and the [[stoney core: OpenLDAP directory data organisation|LDAP Data Backend]] (stoney core: OpenLDAP directory data organisation). | This specification puts together the [[stoney core: Customers Resource - REST API|Customers frontend API]] (stoney core: Customers Resource - REST API) and the [[stoney core: OpenLDAP directory data organisation|LDAP Data Backend]] (stoney core: OpenLDAP directory data organisation). | ||
| + | |||
| + | If nothing else is defined, address related information is always taken out of the billing address (ou=address,uid=<UID>,ou=customers,dn=stoney-cloud,dc=org). | ||
[[Category:Mapping (REST - LDAP)]] | [[Category:Mapping (REST - LDAP)]] | ||
Revision as of 11:11, 26 May 2014
Overview
The customers resource mapping describes the business logic behind the LDAP to JSON transformation and visa versa for the request and response objects. The actual customers resource REST API is located in the REST API category and is named stoney core: Customers 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 Customers frontend API (stoney core: Customers Resource - REST API) and the LDAP Data Backend (stoney core: OpenLDAP directory data organisation).
If nothing else is defined, address related information is always taken out of the billing address (ou=address,uid=<UID>,ou=customers,dn=stoney-cloud,dc=org).
