[Date Prev][Date Next]
Re: options to maintain computed attributes?
- To: "firstname.lastname@example.org" <email@example.com>
- Subject: Re: options to maintain computed attributes?
- From: Jephte Clain <firstname.lastname@example.org>
- Date: Fri, 4 Dec 2015 15:22:00 +0400
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=univ-reunion-fr.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type:content-transfer-encoding; bh=pKU+FWcYc33Z5KSrk0gA1Q6EJmcWCNOKbFDLJCOEsWs=; b=WANSi5bkDQvP9un7zArsYzVIiuof7pZrb0xMFmb6XIWw1bVsffmrhuanfA6325it4a VvVcWtBdagzg0Iv4lstqfP+8kFIiDHfaLxfOPAFWRSw/+EuITKimP39sXXrYHmpvrmOG dzJhKilU5mCgRBQyBgFyqFTGaronitJ6G6JfwE/hyMyFTGsRjDj0e6Ol1jGyHUrW28kX 2ha3/w85G7klnQocJcysDABuaZTNYXf1UfCAoLyh3JTqQsgEURB3XFCeIPtyoIVrtJwI NK/X7yqDk/+As2p3QyKaIZfLJ1rNSZP04t81ZFpZrWydotupLJhxp9n/xEQ+hpuVrfLw i+Mg==
- In-reply-to: <566160F3.email@example.com>
- References: <566160F3.firstname.lastname@example.org>
I searched a bit and found a paper by luke howard about extending openldap
what is the state of native plugins with respect to slapi plugins?
which is better (read: simpler to implement) for the need expressed
Indeed, I also found a comment by Howard Chu on
""""SLAPI is defined by Sun/Netscape, you can refer to their documentation.
Probably would do better discussing this on the openldap-technical
mailing list. And of course, I would have written a native slapd
overlay instead, SLAPI is slower and clumsier."
I was able to find some documentation about slapi on oracle site, but
I can't manage to find any docs about native plugins. maybe I'm just
slapd.plugin manpage seems to be about slapi plugins only
for those who know slapi plugins: am I right to believe the computed
attribute created with "object" type plugins are dynamic? I mean they
are not stored in the backend but "created" each time the attribute is
thanks in advance for any insights. best regards,
2015-12-04 13:46 GMT+04:00 Jephte Clain <email@example.com>:
> 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
> objects accordingly?
> - 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
> *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
> www.univ-reunion.fr <http://www.univ-reunion.fr> || Facebook
> || Twitter <http://twitter.com/univ_reunion>
Jephté CLAIN | Développeur, Intégrateur d'applications
Service Système d'Information
Direction des Systèmes d'Information
Tél: +262 262 93 86 31 || Gsm: +262 692 29 58 24