Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.


Info

This page provides a detailed explanation of Registry Enrollment for versions up to (and including) v0.9.3. For information on Registry Enrollment in newer versions, see Registry Enrollment (Rev 2, Registry 0.9.4 and later). For information on configuring enrollment, see Registry Enrollment Flow Configuration.

By default, COmanage Registry uses an invitation based enrollment flow.

However, COmanage Registry Enrollment can be customized. It is controlled by two configurations:

...

The Registry Enrollment model is designed to support the following models:

  • Federated Identity: Authentication happens at a home institution's IdP. Attributes may or may not be retrieved. self_require_authn or admin_require_authn must be enabled.
  • IdP of Last Resort: The CO will manage the user's credentials. self_require_authn or admin_require_authn may both be disabled. The early provisioning step is intended to support this model – allowing the creation of credentials before the user authentication step.
  • Account Linking: An individual known to the platform has more than one IdP, and would like the identities asserted from each IdP linked to the same profile.

Gliffy Diagram
sizeL

...

displayNameRegistry CMP Enrollment

...

name

...

Registry CMP Enrollment

...

pagePin

...

37