Re: [defaultsynchandler] make default sync handler more customisable (Was: [ldap sync] prepopulate a set of users)

2015-06-15 Thread Nicolas Peltier
cool, let’s go with this, then :-) > On 13 Jun 2015, at 07:14, Tobias Bocanegra wrote: > > btw: I worked on OAK-2948 and moved the SyncContext to an exported > package. the copy-paste overhead of a new synchandler is now minimal, > and you can then just extend from the DefaultSyncContext. let me

Re: [defaultsynchandler] make default sync handler more customisable (Was: [ldap sync] prepopulate a set of users)

2015-06-12 Thread Tobias Bocanegra
btw: I worked on OAK-2948 and moved the SyncContext to an exported package. the copy-paste overhead of a new synchandler is now minimal, and you can then just extend from the DefaultSyncContext. let me know if you need more override points. regards, toby On Fri, Jun 12, 2015 at 11:48 AM, Tobias B

Re: [defaultsynchandler] make default sync handler more customisable (Was: [ldap sync] prepopulate a set of users)

2015-06-12 Thread Tobias Bocanegra
Hi, On Mon, Jun 8, 2015 at 9:06 AM, Nicolas Peltier wrote: > Hi Tobias, > > as discussed off list, this defaultsynchandler customisation discussion we > had joins the one started here [0]. So i’ll dump my findings, and we can see > in which directions to go (or in which direction patches are th

[defaultsynchandler] make default sync handler more customisable (Was: [ldap sync] prepopulate a set of users)

2015-06-08 Thread Nicolas Peltier
Hi Tobias, as discussed off list, this defaultsynchandler customisation discussion we had joins the one started here [0]. So i’ll dump my findings, and we can see in which directions to go (or in which direction patches are the more welcome ;-) First, as is, it’s not about making only this clas

Re: [ldap sync] prepopulate a set of users

2015-05-15 Thread Nicolas Peltier
Ok let’s do this, i might do the same with LdapIdentityProvider (paged search, see other thread), once i got those working, we’ll create appropriate JIRAs. Thanks, Nicolas > On 14 May 2015, at 20:31, Tobias Bocanegra wrote: > > Hi Nicolas, > > On 14 May 2015 at 07:20:47, Nicolas Peltier (npelt

Re: [ldap sync] prepopulate a set of users

2015-05-14 Thread Tobias Bocanegra
Hi Nicolas, On 14 May 2015 at 07:20:47, Nicolas Peltier (npelt...@adobe.com) wrote: Hi Tobias,  thanks a lot for those infos. I just realised i need to implement some custom behaviour to the synchandler, however there is already quite a (big) piece in DefaultSyncHandler. Unfortunately, Default

Re: [ldap sync] prepopulate a set of users

2015-05-14 Thread Nicolas Peltier
Hi Tobias, thanks a lot for those infos. I just realised i need to implement some custom behaviour to the synchandler, however there is already quite a (big) piece in DefaultSyncHandler. Unfortunately, DefaultSyncHandler is located under private impl package and will not be available to my appl

Re: [ldap sync] prepopulate a set of users

2015-05-06 Thread Tobias Bocanegra
Hi, have a look at the SyncMBeanImpl [1] that does something similar. you might be even able to use the MBean from your code. Regards, Toby [1] https://github.com/apache/jackrabbit-oak/blob/jackrabbit-oak-1.2.2/oak-auth-external/src/main/java/org/apache/jackrabbit/oak/spi/security/authenticati

Re: [ldap sync] prepopulate a set of users

2015-05-06 Thread Nicolas Peltier
To be clearer, said in a different way, i’d like to pull a given set of users (LDAP query) from a LDAP server in a scheduled manner, using at most the oak code :-) Nicolas > On 06 May 2015, at 11:09, Nicolas Peltier wrote: > > Hi, > > i’m implementing an application where users can look at ea

[ldap sync] prepopulate a set of users

2015-05-06 Thread Nicolas Peltier
Hi, i’m implementing an application where users can look at each other’s profile, which data comes mainly from a LDAP server. I was wondering how feasible it was to tweak user sync to achieve this, as i am under the impression reading the documentation [0] that sync is only designed to be done