openldap-em-users Mailing List for OpenLDAP Event Manager Overlay
Status: Beta
                
                Brought to you by:
                
                    esimone
                    
                
            You can subscribe to this list here.
| 2007 | Jan | Feb | Mar | Apr (1) | May | Jun | Jul | Aug | Sep | Oct | Nov | Dec | 
|---|
| 
      
      
      From: Ettore S. <ett...@gm...> - 2007-04-24 11:19:03
      
     | 
| Hi,
I'll shortly answer to your questions:
1) All the handler receive a LDIF or DSML stream. More in deep it
will receive the format specified in the associated policy object by
the 'dataFormat' field.
1.3.6.1.4.1.24119.1.0.1.2.2.1 NAME 'policy'
                DESC 'Event Manager policy entry'
                SUP top ABSTRACT
                MUST ( cn $ dataFormat )
                MAY ( userPassword $ description $ searchBase $
                searchFilter $ searchAttribute $ active $
                autostart $ command $ logLevel $ writeAttribute $
                createEvent $ modifyEvent $ deleteEvent ) )
2) Yes, both LDIF and DSML in case of delete, modify or modrdn
provides old and new values.
A ldapmodify of:
dn: uid=mosaico,ou=people,o=H4T,c=IT
changetype: modify
delete: givenName
-
replace: sn
sn: Mosaico
will pass to the handler the following DSML:
<?xml version="1.0" encoding="UTF-8"?>
<batchRequest xmlns="um:oasis:tc:DSML:2:0:core">
  <modifyRequest dn="uid=mosaico,ou=people,o=H4T,c=IT">
    <modification name="givenName" operation="delete">
      <value>Mosaico</value>
    </modification>
    <modification name="sn" operation="delete">
      <value>Gestionale</value>
    </modification>
    <modification name="sn" operation="add">
      <value>Mosaico</value>
    </modification>
  </modifyRequest>
</batchRequest>
3) Yes. The collection of events, the filter of relevant events for
the policies and the handling of them are done by separated threads.
All transparent from LDAP server.
OpenLDAP manage operations as a kind of transaction, so if there are
no bugs in the locking interaction from the overlay and the server
backends the consistence is guaranteed.
Ettore
On 4/24/07, Chaos Eternal <cha...@gm...> wrote:
> hi Ettore,
>   Very glad to get your reply.
> I have the following questions:
> 1. what's the input of our handler, especially for a shell handler
> 2. can I access the data before change? for example, when a ldap
> modify event comes, can I know both the original value and the
> modified value of the target attribute?
> 3. can I access the directory in a consistent manner when an event comes.
>
>
>
> On 4/23/07, Ettore Simone <ett...@gm...> wrote:
> > Hi Chaos,
> >
> > I have only a yet unfinished introduction to the project, but no clean
> > technical or user documentation.
> > This could be the time to write it.
> > How can I help you in the while?
> >
> > Ettore
> >
> > On 4/23/07, Chaos Eternal <cha...@gm...> wrote:
> > > hi simone:
> > >   I found openldap-em project is very interesting and useful.
> > > but i really need some more details about this project.
> > > when i get more documents about it, i may do more contribution.
> > >
> > > thanks
> > >
> > >
> > > --
> > > Best Regards
> > > Chaos Eternal
> > >
> >
>
>
> --
> Best Regards
> Chaos Eternal
>
 |