Grouper Developers Forum

[Chris Hyzer <>]

 

> In my organization we are intending to create a provisioning connector

> (similar to LDAPPC) that will connect to Oracle’s Siebel CRM product.

>

> A potentially good starting point that I’ve discovered is the EsbConsumer,

> which implements ChangeLogConsumerBase.  In fact, this code looks like it

> could be easily extended to create a very easy provisioning connector. 

> Most of the “scaffolding” functionality is built into EsbConsumer, to the

> extent that a developer only needs to create a “publisher” (a subclass

> of EsbListenerBase) and then configure it in grouper-loader.properties.

>

> However, there’s one major drawback: the EsbListenerBase abstract class

> defines the “dispatchEvent” event method as taking a JSON string parameter. 

> I think it would be much more effective if the API instead accepted a

> single EsbEvent  object as the parameter of the “dispatchEvent” method. 

> This would then turn EsbConsumer into a generic provisioning connector

> (which would probably mean it could be renamed).

>

> We actually have made these modifications for our implementation, and

> we’d love to share them with the community if you think they would be beneficial.

 

Note you can convert back to JSON to the beans if you like J.  Also note that you

would get multiple EsbEvents, not just one.  That said, I do think your idea is good,

Rob owns this code, Rob, what do you think?

 

>

> Also, what are your thoughts regarding using the change log in this way

> for provisioning access based on group membership.  Is this a reliable

> method?  For others using this method, do you find it necessary to

> periodically compare group membership within Grouper with the corresponding

> data in the external system to make sure that they are still consistent?

 

I think it is reliable, but you should always sync up periodically just in case J

 

Thanks,

Chris