Grouper Users - Open Discussion List

[Chris Hyzer <>]

FYI, Penn launched this into production for Jira and Confluence.  Before the deployment, I added some more features:

 

1.       There is an external authenticator (with backdoor that admins can use in non prod), to use with web server authn plugins (e.g. shib, cosign, etc)

2.       XMPP notifications so that the normal cache can be long (e.g. 24 hours), but real time updates can be sent from the grouper-loader daemon process (I say real time, but in reality it is 1-2 minutes for an update to propagate)

3.       Fail-safe cache.  You can set this to something long, e.g. 48 hours, where if a call to Grouper fails, it will read from this second level cache so that interruptions in Grouper WS service will not affect Jira/Confluence.  Note this is stored in memory, so if Jira/Confluence is restarted then the cache is cleared and Jira.Confluence will not be available

4.       Implemented the credentials provider, since if off loading groups and profiles, you need this component so when Atlassian asked the credentials provider if it is a valid user, the connector can ask Grouper if the user is in the correct users group (configurable).  I didn’t think we originally needed this but I think Atlassian sometimes mixes authn and authz…

 

https://spaces.internet2.edu/display/Grouper/Grouper+Atlassian+connector

 

Thanks,

Chris

 

From: Chris Hyzer
Sent: Sunday, December 19, 2010 12:59 AM
To: ''
Subject: grouper atlassian connector

 

Hey,

 

If anyone wants an alternative to the Atlassian (jira/confluence) LDAP connector, I wrote an Atlassian-Grouper WS connector.  It is read/write and implements the access (groups) and profile (name/email) provider open symphony interfaces.  We haven’t put this in prod yet at Penn, we are still testing it.  If anyone is interested let me know.

 

https://spaces.internet2.edu/display/Grouper/Grouper+Atlassian+connector

 

Thanks,

Chris