Grouper Users - Open Discussion List

["Black, Carey M." <>]

Jacob,

 

It depends on how you are getting that data into grouper. And maybe the version your using. ( Providing more environment/process details can get you better answers. J )

 

If you are using the grouper loader, then look in the grouper-loader.properties file for these sections:

“

######################################

# Fail-safe 1 - Each individual group

######################################

….

############################################

# Fail-safe 2 - Group list - managed groups

############################################

“

 

Hope that helps.

 

--

Carey Matthew

 

From: [mailto:] On Behalf Of Farmer, Jacob
Sent: Tuesday, January 16, 2018 5:30 PM
To:
Subject: [grouper-users] Preventing runaway group membership changes

 

Colleagues,

 

In our legacy IAM infrastructure, we generally have a series of safety valves which watch for abnormally high numbers of changes and pause processing until a human can review the data. The root cause of this is generally some kind of accidental data change upstream of us – a partially generated extract, etc.

 

Is there a way to do something similar in Grouper-based environment? Essentially, to say “it looks like we’re about to drop 80% of a group’s members; pause that and alert the person on call to take a look at it.”

 

I can’t find anything obvious and we thought about creating something to watch the changelog, but I felt it would be worthwhile to query the collective wisdom of this group.

 

Thanks!

Jacob