| ... | ... | @@ -3,11 +3,11 @@ |
|
|
|
|
|
|
|
### Purpose
|
|
|
|
|
|
|
|
LdapAlias is a plugin which allow to manage ldap aliasedObjectName.
|
|
|
|
LdapAlias is a plugin which allow to manage ldap alias objectClass
|
|
|
|
|
|
|
|
### Fonctionality
|
|
|
|
### Functionality
|
|
|
|
|
|
|
|
It will allow to create alias on objects on other part of the ldap tree to make them appears in only one branch.
|
|
|
|
It will allow to create alias on objects on other part of the ldap tree to make them appears in any branch. They will be stored under aliasRDN, ou=alias by default.
|
|
|
|
|
|
|
|
### Problem
|
|
|
|
|
| ... | ... | @@ -15,8 +15,6 @@ Applications searching the LDAP will be able to follow aliases if they support t |
|
|
|
|
|
|
|
This can be done by setting the LDAP option **LDAP_OPT_DEREF** to **LDAP_DEREF_ALWAYS**. ldapsearch supports this with option "-a always".
|
|
|
|
|
|
|
|
This seems to match LDAP option **LDAP_OPT_DEREF** ldap_set_option
|
|
|
|
|
|
|
|
### Solution
|
|
|
|
|
|
|
|
We create a plugin in FusionDirectory that manage aliasedObjectName attributes.
|
| ... | ... | @@ -33,9 +31,8 @@ objectClass: extensibleObject |
|
|
|
|
|
|
|
#### Management list
|
|
|
|
|
|
|
|
We should a a management class in FusionDirectory that manage this kind of objects, and allow to create new aliasedObjectName attributes.
|
|
|
|
We should a a management class in FusionDirectory that manage this kind of objects, and allow to create new alias objects.
|
|
|
|
|
|
|
|
When we create a new aliasedObjectName attributes we should use :
|
|
|
|
When we create a new alias object we should use :
|
|
|
|
|
|
|
|
* a UsersAttribute for selecting the user is linked to for user alias
|
|
|
|
* a xxxAttribute for selecting the user is linked to for group alias |
|
|
|
* a ObjectSelect for selecting all kind of objects |
