Open Office Hours - May 6

Do you have a question about deploying or configuring Registry or Match? Want to get some input on a solution architecture design? Want to hear how your colleagues in the community are solving problems similar to yours? Each month you can bring your topics for discussion to the call. No need to register or spin up a presentation (but feel free if it suits you!); just show up! A short conversation starter kicks off each session to help get the discussion started.

Friday, May 6 at 12:00 PM (America/New York) (no registration necessary)
https://illinois.zoom.us/j/84190579924?pwd=a1R6Q3VjWi92SHRETlVDMEthZVJYZz09

IN YOUR TIMEZONE & link for your calendar

May's Topic Aperitif: CILogon

CILogon provides a hosted, integrated, and open source identity and access management platform for research collaborations, combining federated identity management with collaborative organization management provided by COmanage Registry. Learn about the great work of CILogon during this 15 min chat, after which we’ll continue with topics of your choosing. Bring your questions, comments, and suggestions about any topic to office hours with the COmanage project team.

COmanage Community and Resources

Over the past several months, we have been adding pages to the COmanage wiki to help bundle related information with additional context on how these pieces are related. We are hoping that, in particular, those newer to COmange will find these pages helpful in discovering the rich information in the wiki. This month we added a page to highlight the wiki resources available to support the COmanage Community.

COmanage News

This newsletter section is designed to provide additional transparency on the day-to-day workings of COmanage. Have ideas about other information that we should be including? Let us know on the #incommon-comanage slack channel or by emailing Laura!

Match 1.0.0 - RC3 is available

We published Release Candidate 3 on Friday, April 29. We encourage those exploring Match for its first release to install this version. Please report any issues via JIRA or Slack. We expect to release RC4 or 1.0.0 final around mid-May, depending on what we hear back.

Getting the Latest Version

• Release Candidate:
  https://github.internet2.edu/COmanage/match/releases/tag/1.0.0-rc3
• TAP Container Version:
  https://spaces.at.internet2.edu/display/ITAP/InCommon+Trusted+Access+Platform+Release 

Installation Information

• Installation & Configuration Information:
  https://spaces.at.internet2.edu/display/COmanage/COmanage+Match+Technical+Manual
• Information for Updating from Previous Versions:
  https://spaces.at.internet2.edu/display/COmanage/Upgrading+Match 

FAQ: Most Asked? CO vs COU

The number one question that we are asked about COmanage once folks start to use it is the difference between the CO and COU objects and when to use each. While many organizations have natural subdivisions within them, the reason that you would divide your CO into COUs is that there are differences across your CO that necessitate different policies in one or more of the following:

• How individuals join and/or leave
• Differing rules about how applications get provisioned or de-provisioned
• Who manages person membership and privileges
• The information stored or used about members

Basically, if your collaboration, a single entity with common goals, has unique requirements among the different groups and/or departments regarding how participants will join those parts of your collaborations, then, you have a CO that contains COUs.  If you have only one common set of policies that define how individuals are added or removed from the CO, then you do not have COU even though you may have groups for simple access control.

Want to learn more? We encourage you to head to our wiki for a deeper explanation and a use case.

That’s it for this month’s newsletter; keep an eye out for our next one scheduled for late May. We hope to see you during our Open Office Hours on May 6th!