grouper-dev - Draft Minutes: Grouper Call 27-May-09
Subject: Grouper Developers Forum
List archive
- From: Emily Eisbruch <>
- To: Grouper Dev <>
- Subject: Draft Minutes: Grouper Call 27-May-09
- Date: Tue, 2 Jun 2009 08:24:05 -0400
Grouper Call 27-May-09** *Attending*
Tom Barton, U. Chicago (chair) Gary Brown, Bristol James Cramton, Brown Shilen Patel, Duke Chris Hyzer, U. Penn Tom Zeller, U. Memphis Steve Olshansky, Internet2 Emily Eisbruch, Internet2 (scribe) **New Action Items** [AI] (Chris) will create a Jira issue for configurable namespace/customizable stem identifier. [AI] (Chris) will prepare the Grouper 1.4.2 release. (TomB) and (Chris) will update the Release Steps wiki page. [AI] (TomZ) will send the group a code sample illustrating use of the Shibboleth Attribute Resolver for incremental provisioning and ldappc. [AI] (TomZ) will email Steven, with a cc to TomB, describing the plan to use the Shibboleth Attribute Resolver. [AI] (Chris) will publish a specification of the notification consumer's behavior in Grouper 1.5. This will inform TomZ’s work on incremental provisioning and ldappc. *Carry Over Action Items* [AI] (RL Bob) will email the Grouper lists to ask if people are interested in a configurable namespace approach. [AI] (TomB) will start a wiki page on attribute framework for Grouper, including information on handling of custom versus non-custom fields/attributes. **Discussion** *Configurable namespace delimiter* Chris did some research and concluded that the configurable namespace approach is not completely straightforward, but it may be worthwhile. Suggestion: The biggest problem with the current approach of having colons is the problem in interfacing with Active Directory. So should a “fool me” mode be considered, where the UI or the API can optionally change the delimiter symbol “on the way out”? Problem: This approach could be tricky, especially if the chosen delimiter character is already being used in the stem name. U. Chicago has worked with Active Directory and has encountered some of the same issues as U. Washington. But there seem to be work-arounds, such as not putting group names in SAM account names. Tom recalled that early on in development of Grouper, using configurable namespace was considered, but a shortcut was taken. Configurable namespace delimiter -- using a restricted set of possible characters -- would be the best approach. Then a conversion task is required if a site converts to a different delimiter afterwards. [AI] (Chris) will create a Jira issue for configurable namespace/customizable stem identifier. *Jira Management* Tom reminded the group to make sure Jira issues are assigned to the right release. Be sure Jira issues are updated and have the correct status *Grouper 1.4.2 Release*
TomB won’t be able to handle the packaging and PR for Grouper 1.4.2 until weekend of Sat. June 6. Chris will take care of that. SteveO will provide Chris the web permissions to handle the release. [AI] (Chris) will prepare the Grouper 1.4.2 release. (TomB) and (Chris) will update the Release Steps wiki page. Chris will make new wiki pages for documenting Grouper 1.5 *Ldappc and Shibboleth Attribute Resolver* TomZ has been considering whether to use Shib Attribute Resolver as a basis for ldappc or not. The idea is that we would use the Shib Attribute Resolver as a basis, and write the group specific semantics and a new data connector that are needed for our purposes. If ldappc will ever want to provision groups / attributes from a data source other than Grouper, then the approach of using the Shib Attribute Resolver, makes sense as it offers flexibility. Grouper is not strong at handling named value pairs. The Shib Attribute Resolver would handle this. It’s an advantage that others are successfully using the Shibboleth Attribute Resolver. It is a plus to reuse things across the Internet2 middleware projects. TomZ suggested using Spring to replace the Configuration Manager. The config file would remain as is, but we’d used Spring to parse it instead of the Config. Manager. [AI] (TomZ) will send the group a code sample illustrating use of the Shibboleth Attribute Resolver for incremental provisioning and ldappc. [AI] (TomZ) will email Steven, with a cc to TomB, describing the plan to use the Shibboleth Attribute Resolver. [AI] (Chris) will publish a specification of the notification consumer's behavior in Grouper 1.5. This will inform TomZ’s work on incremental provisioning and ldappc. Tom suggested in made sense for the first post 1.5 version of ldappc version to handle incremental provisioning without incorporating the Shib Attribute Resolver. Schedule incorporation of Shib Attribute Resolver for a later release. TomZ noted there are requirements to use the enhanced ldappc locally at U Memphis. But the incorporation of the Shib Attribute Resolver is not an urgent requirement. Q: Chris asked, is ldappc incremental provisioning going to work in the Grouper Loader? A: Yes, and it will also be possible to do incremental provisioning outside of the loader. Loader process will also be important for implementing notifications. *Collaboration with uPortal in France* The Grouper and uPortal projects are forming a cooperative effort to help the French ESUP Portail develop some group capabilities based on Grouper. The plan is to have both uPortal and Grouper developers assist the French effort. Timeframe is this summer. The result should be easily importable into the main uPortal branch in the future. Some Grouper toolkit enhancements may result. Next Call: Wed. 10-Jun-09, Noon ET Emily Eisbruch, Technology Transfer Analyst Internet2 office: +1734-352-4996 | mobile +1-734-730-5749 ESCC/Internet2 Joint Techs July 19-23, 2009 - Indianapolis, Indiana http://jointtechs.es.net/indiana2009/ Emily Eisbruch, Technology Transfer Analyst Internet2 office: +1734-352-4996 | mobile +1-734-730-5749 ESCC/Internet2 Joint Techs July 19-23, 2009 - Indianapolis, Indiana http://jointtechs.es.net/indiana2009/ |
- Draft Minutes: Grouper Call 27-May-09, Emily Eisbruch, 06/02/2009
Archive powered by MHonArc 2.6.16.