Skip to content
Permalink
master
Switch branches/tags

Name already in use

A tag already exists with the provided branch name. Many Git commands accept both tag and branch names, so creating this branch may cause unexpected behavior. Are you sure you want to create this branch?

COmg-CO101-intro/_episodes/02-identityRegistries.md

Go to file
Some word smithing and filled out two small sections.
Latest commit f55b73b Nov 14, 2019 History 
Some word smithing and filled out two small sections about capabilities.
1 contributor

Users who have contributed to this file

2. About Identity Registries What is an identity registry? A bit of history Some review: What is COmanage again?
77 lines (55 sloc) 3.57 KB
Raw Blame
title teaching exercises questions objectives keypoints workshopOverviewName workshopOverviewURL lessonOverviewName lessonOverviewURL previousEpisodeName previousEpisodeURL nextEpisodeName nextEpisodeURL
Identity Registries
5
0
Question here
List the objectives
List the key takeaways for the episode
COmanage Workshop: Managing Identities & Collaborations
CO101 - Workshop Intro & Getting to Know COmanage
../index.md
1. Workshop Welcome
/_episodes/01-orientation.md
3. Why COmanage
/_episodes/02-whyCOmanage.md

2. About Identity Registries

COmanage is an Identity Registry. What is a registry?

What is an identity registry?

An Identity Registry is a database for storing, curating, and managing electronic identities for people. The primary purpose for creating a registry is to manage your users' access to electronic services.

A key benefit to storing this information in a registry rather than a file, spreadsheet or general purpose database is because registries provide pre-configured features to enable sharing of information about the registered people with “downstream” services. Registries can help manage who will gain access to these services, either directly or through a secondary system that works with COmanage.

A bit of history

Despite the usefulness of registries, there is no universal incumbent product that is used. For many years, each university wrote its own identity registry to satisfy its own local use cases; many universities still take this approach. More recently, some universities have been working together to create a "Registry for Higher Education and Research" (with mixed success.) There also are newer enterprise and open source efforts have been aimed at organizations of different sizes.

We'll talk about capabilities later...some tools in this space include:

  • COmanage
  • midPoint
  • WSO2 Identity Server
  • KeyCloak
  • OpenIAM
  • Apache Syncope
  • OpenAM
  • Microsoft AD
  • Microsoft Identity Manager 2016
  • NetIQ (Novell) Identity Manager
  • IBM Tivoli Identity Manager
  • Oracle Identity Manager
  • ForgeRock Identity Platform

Some review: What is COmanage again?

COmanage is a Collaboration Management Platform (CMP) designed and built for federated identity environments. These CMP tools provide many things:

  • An interface for user enrollment
  • The ability to assign rights and permissions to people through roles, groups, etc
  • The ability to distribute the management of rights and permissions to multiple people. For example, a project's Principal Investigator can manage the rights and permissions for his/her project group

COmanage is not the only CMP focused on federated identity. Examples of other services include HEXXA and PERUN.

Deployers often strongly prefer one tool over another, though at their core, each of these tools serve the same basic functions. Their differences are primarily in the emphasis each tool makes on various features, how the development of the tool is managed, and how the tool is packaged with other tools.

Since you are here, we are assuming that you have already made the choice to invest in learning COmanage.

NEXT SECTION: 3. Why COmanage

PREVIOUS SECTION: 1. Workshop Welcome

LESSON OVERVIEW: CO101 - Workshop Intro & Getting to Know COmanage

WORKSHOP OVERVIEW: COmanage Workshop: Managing Identities & Collaborations