Changes

= Auth action Action === Auth retrieval Retrieval (GET) ==The following sequence describes the authentication and role retrieval:# Look-up the user in the OpenLDAP directory (with a configurable service user):#: Currently, this will be cnin the ou=Managerpeople,dc=stoney-cloud,dc=orgsub tree (with a configurable LDAP service user):#: Later on, this will be a [[stoney_corefilter:_OpenLDAP_directory_data_organisation#Services | service user]]<code>(mail=name.surname@example.com)</code>#: scope: <code>one</code># If the user exists, use the retrieved DN and try to bind with the it (a working LDIF is described under [[stoney_core:_OpenLDAP_directory_data_organisation#People_uid_.28per_person.29 | users credentials]]).#: bind dn: <code>uid=<UID>,ou=people,dc=stoney-cloud,dc=org</code>#: password: <code>myverysecretpassword</code># If the bind was successful, retrieve the users [[stoney_core:_OpenLDAP_directory_data_organisation#People_Roles | roles]] further information with the LDAP service userfrom the leaf uid=<UID>,ou=people,dc=stoney-cloud,dc=org.

An example how to bind with the user credentials, presuming uid=<UID>: ldapsearch -H ldaps://ldapm.stoney-cloud.org -b "ou=people,dc=stoney-cloud,dc=org" -D "uid=<UID>,ou=people,dc=stoney-cloud,dc=org" -x "(objectclass=*)" -v -W Information about the configurable LDAP service user:* Currently, the LDAP service user is cn=Manager,dc=stoney-cloud,dc=org* Later on, this will be a [[stoney_core:_OpenLDAP_directory_data_organisation#Services | LDAP service user]]. === Auth Retrieval (GET) Mapping ===

| colspan=4 id| [[stoney_core:_OpenLDAP_directory_data_organisation#Reseller_Billing_Address | Reseller Billing Address]]uid

|user| address.gender || ou=address,uid=4000000,ou=reseller || sstGender || mail