Difference between revisions of "stoney core: OpenLDAP directory data organisation"
(→Reseller Customers) |
(→Reseller Employees) |
||
Line 261: | Line 261: | ||
==== Reseller Employees ==== | ==== Reseller Employees ==== | ||
− | The sub tree '''ou=employees,uid=4000000,ou=reseller,dc=stoney-cloud,dc=org''' contains the employees belonging to the reseller '''Reseller Ltd.''' (all the employees with the the attribute sstBelongsToEmployeeUID=4000000). With the attribute labeledURI we use the functionality of the [http://www.openldap.org/doc/admin24/overlays.html#Dynamic%20Lists dynamic lists overlay] to automatically give us a list of employees belonging to this reseller. | + | The sub tree '''ou=employees,uid=4000000,ou=reseller,dc=stoney-cloud,dc=org''' contains the employees belonging to the reseller '''Reseller Ltd.''' (all the employees with the the attribute sstBelongsToEmployeeUID=4000000). With the attribute labeledURI we use the functionality of the [http://www.openldap.org/doc/admin24/overlays.html#Dynamic%20Lists dynamic lists overlay] to automatically give us a list of employees belonging to this reseller. The number of employees is always the same or smaller than the number of people belonging to a reseller (they are a subset). |
dn: ou=employees,uid=4000000,ou=reseller,dc=stoney-cloud,dc=org | dn: ou=employees,uid=4000000,ou=reseller,dc=stoney-cloud,dc=org |
Revision as of 13:39, 24 July 2013
Contents
Abstract
This document describes the OpenLDAP directory data organisation for the stoney cloud. This directory is the only database for all the services, which are manageable through the web interface of the stoney cloud.
Some titles have numbers in brackets. These numbers reflect the stoney cloud version, in which these entries have been added or modified.
Introduction
All Service-, User- and Billing-Data ist stored in the OpenLDAP directory. The directory runs in Multi-Master Mirror-Mode for high availability.
Data Organisation
The following chapters explain the data organisation of the stoney cloud OpenLDAP directory.
root
The following LDIF shows the root entry of the whole OpenLDAP directory tree for the stoney cloud:
dn: dc=stoney-cloud,dc=org objectclass: top objectclass: dcObject objectclass: organization dc: stoney-cloud o: stoney-cloud
The following LDIF shows the root of the whole OpenLDAP directory tree for the stoney cloud modified for the company stepping stone GmbH in Switzerland:
dn: o=stepping-stone,c=ch objectclass: top objectclass: organization o: stepping-stone
The entry c=ch stands for the country code of Switzerland while o=stepping-stone stands for the the organisation stepping-stone. The entry stepping-stone is in the process of being reserved at the Federal Office of Communications. With the reservation of the name, all the directory entries will be unique over the whole world.
The root entry can be chosen during the installation process of the stoney cloud. If you decide to use the default entry, you'll end up with dc=stoney-cloud,dc=org.
Administration
Configuration
Customers
Groups
People
Reseller
The sub tree ou=reseller,dc=stoney-cloud,dc=org contains all the resellers. Each reseller has a unique uid, which is used for later reference.
Reseller uid (per Reseller)
The following LDIF shows you the default reseller entry after a fresh stoney cloud installation. All relevant data belonging to this reseller are stored below this dn.
dn: uid=4000000,ou=reseller,dc=stoney-cloud,dc=org objectclass: top objectclass: sstReseller uid: 4000000 organizationName: Reseller Ltd. sstBelongsToResellerUID: 4000000 sstIsActive: TRUE
The following table describes the different attributes:
Attribute | |
|
Description |
uid | |
|
A unique integer value with 7 digits or more. For example: 4000000. |
organizationName | |
|
The organisation name of the reseller. For example: Reseller Ltd.. |
sstBelongsToResellerUID | |
|
Stores the reseller UID the leaf belongs to. A unique value with 7 digits or more, must correspond with the uid entry. For example: 4000000. |
sstIsActive | |
|
Is the entry active? Either yes (TRUE) or no (FALSE). |
Legend:
- x: Mandatory in all cases.
Reseller Billing Address
The sub tree ou=address,uid=4000000,ou=reseller,dc=stoney-cloud,dc=org contains the billing address:
dn: ou=address,uid=4000000,ou=reseller,dc=stoney-cloud,dc=org objectclass: top objectclass: organizationalUnit objectclass: sstAddressCompany ou: address organizationName: Reseller Ltd. sstGender: m givenName: Name surname: Surname postalAddress: Street Number countryName: CH postalCode: Postal Code localityName: Locality preferredLanguage: en-GB mail: name.surname@example.com telephoneNumber: +41 00 000 00 00 mobileTelephoneNumber: +41 00 000 00 00 sstWebsiteURL: https://www.example.com/
The following table describes the different attributes:
Attribute | |
|
Description |
organizationName | |
|
Company name, example: stepping stone GmbH |
sstGender | |
|
Either 'm' for male or 'f' for female. |
givenName | |
|
Givenname, example: Hans. |
surname | |
|
Surname, example: Muster. |
postalAddress | |
|
Street Number, example: Neufeldstrasse 9. Multi-lined field. |
postOfficeBox | |
|
Postbox, example: 3456. |
stateOrProvinceName | |
|
Dieses Pulldownmenü soll aktuell nur im Falle der USA überhaupt im Frontend Menü erscheinen. |
countryName | |
|
Country name and code accourding to ISO 3166-1 and the corresponding ISO 3166-1-alpha-2 code , example: Switzerland, CH. |
postalCode | |
|
Zipcode, example: 3012 |
localityName | |
|
City, example: Bern. |
preferredLanguage | |
|
Display language of the user according to RFC 1766, example: de-CH. Currently supported:
|
|
|
E-mail address of the user, example: hans.muster@example.com. | |
telephoneNumber | |
|
Fixnet phone number, example: +41 31 222 33 44. |
mobileTelephoneNumber | |
|
Mobile phone number, example: +41 76 222 33 44. |
sstWebsiteURL | |
URL gemäss RFC-3986 http://tools.ietf.org/html/rfc3986. For example http://www.stepping-stone.ch/. |
Legend:
- x1: Either telephoneNumber or mobileTelephoneNumber need to be present. Both attributes can exist together.
- x2: Either postalAddress or postOfficeBox need to be present. Both attributes can exist together.
- x3: If the countryName is either Canada or the USA, the stateOrProvinceName needs to be present.
Reseller Shipping Address (optional)
The sub tree ou=shipping,uid=4000000,ou=reseller,dc=stoney-cloud,dc=org contains the shipping address and is optional (it is only needed, if the shipping address differs from the billing Address).
dn: ou=shipping,uid=4000000,ou=reseller,dc=stoney-cloud,dc=org objectclass: top objectclass: organizationalUnit objectclass: sstAddressCompany ou: shipping organizationName: Reseller Ltd. sstGender: m givenName: Name surname: Surname postalAddress: Street Number countryName: CH postalCode: Postal Code localityName: Locality preferredLanguage: en-GB mail: name.surname@example.com telephoneNumber: +41 00 000 00 00 mobileTelephoneNumber: +41 00 000 00 00 sstWebsiteURL: https://www.example.com/
Reseller Billing
The sub tree ou=billing,uid=4000000,ou=reseller,dc=stoney-cloud,dc=org contains billing relevant data:
dn: ou=billing,uid=4000000,ou=reseller,dc=stoney-cloud,dc=org objectclass: top objectclass: organizationalUnit objectclass: sstBillingReseller ou: billing sstResellerBill: FALSE
This entry need to be described in detail. TBD.
Reseller Customers
The sub tree ou=customers,uid=4000000,ou=reseller,dc=stoney-cloud,dc=org contains the customers belonging to the reseller Reseller Ltd. (all the customers with the the attribute sstBelongsToResellerUID=4000000). With the attribute labeledURI we use the functionality of the dynamic lists overlay to automatically give us a list of customers belonging to this reseller.
dn: ou=customers,uid=4000000,ou=reseller,dc=stoney-cloud,dc=org objectclass: top objectclass: organizationalUnit objectclass: labeledURIObject ou: customers labeledURI: ldap:///ou=customers,dc=stoney-cloud,dc=org??one?(sstBelongsToResellerUID=4000000) member: uid=4000001,ou=customers,dc=stoney-cloud,dc=org
In this example, the reseller Reseller Ltd. has one customer (with the uid=4000001).
Reseller Employees
The sub tree ou=employees,uid=4000000,ou=reseller,dc=stoney-cloud,dc=org contains the employees belonging to the reseller Reseller Ltd. (all the employees with the the attribute sstBelongsToEmployeeUID=4000000). With the attribute labeledURI we use the functionality of the dynamic lists overlay to automatically give us a list of employees belonging to this reseller. The number of employees is always the same or smaller than the number of people belonging to a reseller (they are a subset).
dn: ou=employees,uid=4000000,ou=reseller,dc=stoney-cloud,dc=org objectclass: top objectclass: organizationalUnit objectclass: labeledURIObject ou: employees labeledURI: ldap:///ou=people,dc=stoney-cloud,dc=org??one?(sstEmployeeOfUID=4000000) member: uid=4000002,ou=people,dc=stoney-cloud,dc=org
In this example, the reseller Reseller Ltd. has one employee (with the uid=4000002).
Reseller People
Im Eintrag ou=people,uid=2000000,ou=reseller,o=stepping-stone,c=ch werden sich die Mitarbeiter des Resellers stepping stone GmbH (die Benutzer mit dem Attribut sstbelongstouid=2000000) aufgelistet. Dieser Eintrag nutzt die Funktionalitäten vom Overlay dynlist, indem im Attribut labeleduri eine Formel eingetragen wird. Die Attribute member werden so „on the fly“ erstellt.
dn: ou=employees,uid=4000000,ou=reseller,dc=stoney-cloud,dc=org objectclass: top objectclass: organizationalUnit objectclass: labeledURIObject ou: employees labeledURI: ldap:///ou=people,dc=stoney-cloud,dc=org??one?(sstEmployeeOfUID=4000000) member: uid=4000002,ou=people,dc=stoney-cloud,dc=org member: uid=4000064,ou=people,dc=stoney-cloud,dc=org member: uid=4000066,ou=people,dc=stoney-cloud,dc=org member: uid=4000069,ou=people,dc=stoney-cloud,dc=org
In this example, four people the reseller Reseller Ltd. (including the employee with the uid=4000002).