COmanage Users List

[Laura Paglione <>]

View in a browser

NEWSLETTER

ISSUE #7 | April 29, 2022

The COmanage Community

One of our favorite parts about working on COmanage is the rich discussions and collaborations that we have with the community members. This group makes COmanage possible and inspires and drives the impact of the software, both in the offered features and how COmanage is used. This month features an Open Office Hours discussion from CILogon, which maintains one of the largest COmanage installations, and an updated wiki landing page for our community resources.

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 include? Let us know on the #incommon-comanage slack channel or by !

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 Question? 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 defining how individuals are added or removed from the CO, 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!

---

About The COmanage Project

COmanage is an Open Source Project that is focused on streamlining digital lifecycle management for your populations. It consists of two tools: Registry and Match. 

COmanage Registry is an identity registry with flexible enrollment and lifecycle management capabilities that helps you meet your identity management objectives using standardized tools and approaches. It can be used as a central person registry, a guest management system, or a collaboration hub for scholarly collaborations.

COmanage Match performs identity de-duplication in order to help minimize the creation of duplicate accounts for the same individual. It provides a heuristic-based system for matching identity records across multiple authoritative systems of record. Match can be used with Registry or as a standalone product complementary to your other tools.

Learn more about the project and its supporters at https://incommon.org/software/comanage/.

---

Q: Why did I get this awesome email? 

A: Because you have subscribed to one of the COmanage mailing lists!
See the COmanage Email Lists wiki page for more details.