I may have a need soon to implement "computed" attributes in LDAP, to
accommodate dumb clients that are unable to properly update the database
for example, an attribute masterAttr may have values like "A:B" (its
value updated by the dumb client), but other clients need the A or B
part separately. So whenever masterAttr is updated with value "A:B",
firstPartAttr have to be updated with "A" and secondPartAttr with "B"
what are my options to achieve this?
- is there an overlay like slapo-rwm but for attribute values? I
searched but did not found anything. So I guess the answer is no.
- using a combination of back-perl, back-relay and slapo-translucent? is
that even possible
- using back-sock as an overlay to monitor modifications and update the
modified objects accordingly?
- a script that monitor the accesslog database and update the modified
- biting the bullet and writing an overlay myself?
before diving too deep into this issue (and possibly drowning), I
figured I would ask. any thoughts? ideas?
thanks in advance, best regards,
*Jephté CLAIN | Développeur, Intégrateur d'applications*
Service Systèmes d'Information
Direction des Systèmes d'Information <http://dsi.univ-reunion.fr>
Tél: +262 262 93 86 31 <tel:+262262938631> || Gsm: +262 692 29 58 24
|| Twitter <http://twitter.com/univ_reunion>