Grouper Users - Open Discussion List

["Hyzer, Chris" <>]

The API method:

 

boolean group.getAttributeDelegate().hasAttributeOrAncestorHasAttribute(String attributeFlagName, boolean checkSecurity)

 

Allows you to easily see if a group or parent folder has an attribute assigned (e.g. for provisioning).  Not sure it can be called from an EL filter… want me to try it?

 

Is kafka messaging?  You want to do an HTTP -> Kafka connector and send from grouper to http?

 

Thanks

Chris

 

From: [mailto:] On Behalf Of Black, Carey M.
Sent: Monday, April 09, 2018 12:11 PM
To: Shaun Koh <>; Mailing List <>
Subject: [grouper-users] RE: EsbHttpPublisher -- el filter for attribute assignments

 

Shaun,

 

I am not an expert on the ESB flavor of Grouper things. But I am poking at the “changelog.consumer” stuff at the moment. And the ESB stuff looks like it is a “changelog.consumer” to Grouper. J

 

 

An option ( that may or may not appeal to you) would be to consider these two general approaches: ( Maybe also could depend on the ESB your talking too. I am not sure…)

1)      Use a single Grouper attribute (and a single ESB publisher) and have the ESB later route/filter/map/duplicate the Grouper stream of messages into ESB queues(“topics”?).

2)      Use a single Grouper attribute per “topic” and have “N” ESB publishers that each only publish to a given topic.

 

I can see advantages in both directions.

                Case 1:

                                Pros:      Smaller Grouper config foot print.  ( Per ESB infrastructure )

                                                Smaller Grouper data(attribute) foot print. (one attribute)

                                                Only one Loader daemon process being added. ( smaller RAM requirement.)

                                Cons:

                                                One big Grouper Change log and all message flow serially. ( may form delays during heavy updates? )

                                                Need to manage ESB config to do “route/filter/map/ duplicate” logic.

                Case2:

                                Pros:      Grouper controlled “topic to data” map.

                                                More (and separate) queues per topic. ( May still form delays but would only affect each topic independently.)

                                Cons:     More Grouper config foot print. (per “topic”)

                                                Likely a larger RAM foot print for the Loader daemon.

                                                (maybe a con, some might see this as an advantage) More Grouper data(attribute) foot print (N attributes).

 

 

Question for you….

                GrouperDAOFactory is a very “low level” api in the system. ( Basically your talking “directly” to the Grouper DB. Which seems like that is the wrong direction to me.) What do you think you need from that deep of an integration level to achieve?

 

--

Carey Matthew

 

From: <> On Behalf Of Shaun Koh
Sent: Monday, April 9, 2018 1:47 AM
To: Mailing List <>
Subject: [grouper-users] EsbHttpPublisher -- el filter for attribute assignments

 

Hi there,

 

I’m currently attempting to configure the EsbHttpPublisher to send messages to a Kafka topic via our ESB platform.

 

While this works with basic el filtering (i.e. using the EsbEvent object), I am wondering if it is possible to filter groups/stems based on an attribute that has been assign to it (e.g. similar to how PSPNG works) ?

 

The methods provided by the GrouperDAOFactory class seem useful though I have been unsuccessful in calling it as it returns matchesFilter: false even with predefined input.

 

It would be great to have some suggestions / workarounds before having to perform any custom extensions.

 

Best Regards,

Shaun K.