Page tree
Skip to end of metadata
Go to start of metadata

CO Email Lists and New Types

Registry v3.1.0 adds the capability to manage CO Email Lists. As part of this, a new default Email Address type "list" (aka "Mailing List") and a new Identifier type "provisioningtarget" have been added. Existing deployments should perform the following steps to define this type for each CO:

  1. Configuration >> Extended Types
  2. Select For Attribute "Email Address"
  3. Click Add/Restore Default Types
  4. Select For Attribute "Identifier"
  5. Click Add/Restore Default Types

Registry v3.1.0 also adds a new default Identifier type, ePUID (for eduPersonUniqueID). Step 5, above, will make this type available.

Collecting Authoritative Attributes From Environment Variables

Registry v3.1.0 introduces the EnvSource Organizational Identity Source plugin as an improved mechanism for collecting attributes from environment variables. The existing mechanism, CMP Enrollment Attributes, remains available, but is deprecated and will be removed in Registry v4.0.0. For more information, see Consuming External Attributes via Web Server Environment Variables.

Provisioning Plugin status() Signature Change

For custom Provisioning Plugins that implement status(), the function signature is now

status($coProvisioningTargetId, $Model, $id)

where $Model can be one of CoEmailList, CoGroup, or CoPerson.

Resized Columns

Registry v3.1.0 makes several database columns wider, however due to a bug in the database migration system (CO-1570) these columns may not be updated automatically on Postgres based deployments. To manually widen the fields, run the following SQL commands:

postgres> alter table cm_co_enrollment_flows alter column redirect_on_confirm type varchar(1024);
postgres> alter table cm_org_identity_source_records alter column sorid type varchar(1024);
  • No labels