Much of COmanage Registry's power comes from its ability to flexibly connect to your other systems, either to obtain information from a Source to use and/or aggregate into your Person Records in Registry, or to Provision (send) processed information from Registry to your other systems. This section describes the Registry structures for these tasks, including

  • Inbound Information, such as Organization Identity Sources or Authenticators;
  • Outbound Information, such as Provisioning targets, Services, and Email lists;
  • Create and manage identifiers to link information found in other systems; and
  • Configuration Resources to aid these connections, such as Registry Connection Servers.


INBOUND: Organizational Identity Sources

Organizational Identity Sources allow for the creation of Organizational Identities linked to an external source or "system of record". These sources can include LDAP servers, REST APIs, SQL databases, flat files, and so on. Custom plugins can be written for arbitrary sources.

INBOUND: Authenticators

Authenticators are used to prove a CO Person's identity to an application or service. An Authenticator combined with an Identifier is a credential.  Because Authenticators are collaboration issued, they are attached to the CO Person, not to Organizational Identities (as for external credentials).

OUTBOUND: Provisioning

Provisioning refers to the action of using Registry data to create or remove access to applications and services. COmanage Registry uses provisioning to provide the data that it stores to applications using one of three models, and in four different modes: Automatic, Manual, Enrollment-based, and Queue-based.

OUTBOUND: Services

As of v2.0.0, COmanage Registry supports a concept of CO Services. A CO Service represents a service or application that a CO Person has access to by participating in the collaboration. While access to the service is likely controlled by Registry managed attributes, the service itself is not accessed as part of Registry. Instead, CO Services act as inventory or catalog of available services, rendering a list of available services on a per CO Person basis.

OUTBOUND: Email Lists

Email Lists are data structures that associate CO Groups and Group Memberships with listservs. Email Lists are available as of Registry v3.1.0.

Identifiers

COmanage Registry is capable of automatically assigning identifiers for objects within COs. Identifiers may be assigned on demand, as part of an Enrollment Flow, or as part of a Pipeline. If you only want to assign identifiers manually (ie: without the help of auto assignment), this page does not apply to you.

CONFIGURATION: Servers

A Registry Server is intended to represent one physical or logical server referenced by the CO. While various Registry configuration objects reference Server objects, they need not be (and so the Server Registry can be used to track endpoints of interest to the CO, whether or not they are used by COmanage Registry specifically).



  • No labels