Salut,
As Clément suggested, I removed the <operations> tag and it
generated something in the dump.csv file:
,cn=maxime,ou=EMPLOYES,ou=PERSONNES,o=ORG,100056
However, as you can see, it doesn't print the "cn" field. This is
maybe because I don't have a <dataset> tag for the attribute "cn" (it
is updated following the default setting).
So from what I understand, this whole <audit> thing is a work in
progress:) Let me know if you want me to test it (or test anything
else!).
Regards,
MaximeSébastien Bahloul <[email protected]> a écrit :
Hi Maxime,
I need to check but I am pretty sure that this feature is not yet
implemented : go through the logback.xml file for now. Sorry about that,
the XML file was designed with a high level view - i.e. avoid to configure
directly any logging API - before most of the code was written.
Regards,
--
Sebastien BAHLOUL
IAM / Security specialist
Ldap Synchronization Connector : http://lsc-project.org
Blog : http://sbahloul.wordpress.com/
Le 19 avril 2012 15:27, Clément OUDOT <[email protected]> a écrit :
Le 19 avril 2012 15:20, Maxime Pelletier <[email protected]> a
écrit :
> Hi Clément,
>
> I added "update" like this:
>
> <operations>create, delete, update</operations>
>
> But it still don't work. The file is created but is empty. Any idea?
Does it
> work for you?
I never tested it. Try to remove the operations markup, it should then
log all operations.
Else, you should still be able to configure audit in the logback.xml
configuration.
_______________________________________________________________
Ldap Synchronization Connector (LSC) - http://lsc-project.org
lsc-users mailing list
[email protected]
http://lists.lsc-project.org/listinfo/lsc-users
_______________________________________________________________
Ldap Synchronization Connector (LSC) - http://lsc-project.org
lsc-users mailing list
[email protected]
http://lists.lsc-project.org/listinfo/lsc-users
