Child pages
  • Upgrading Registry to v2.0.0
Skip to end of metadata
Go to start of metadata

Cron Shell Renamed

Registry v2.0.0 renames CronShell to JobShell. If you have installed a cron job to run CronShell, you will need to update it to call JobShell instead. See also Registry Installation - Cron.

AvailablePlugin Directory

To reduce the overhead of less frequently used plugins, some plugins have been moved to the new app/AvailablePlugin directory. If you are using any of the plugins in this directory, you need to re-enable them by creating a symlink to the appropriate plugin(s) from your local/Plugin directory. For more information, see Installing and Enabling Registry Plugins.

New Default Extended Types

Several new extended types are defined by default. To add these to existing COs, use Configuration >> Extended Types, and for each relevant type click (plus) Add/Restore Default Types.

  • New Address type: Campus
  • New Email Address types: Preferred, Recovery
  • New Identifier types: Badge, Enterprise, National, Network, ORCID, Reference, SORID
  • New Telephone Number type: Campus

Existing defined types will remain unchanged.

Change In Behavior Of Members Groups

As of Registry v2.0.0, the CO and COU Members and Admin Groups and have been renamed. The members groups have been replaced with groups representing all members, and new members group with only active members have been introduced. See the linked documentation for information about the new naming conventions. As part of the upgrade you may need to:

  • Reconfigure or rewrite provisioning targets, and adjust any integrated applications that were relying on the old names. For example, LDAP records may continue to have the old group names until individual records are rewritten.
  • COUs may no longer have a colon (:) in their name.

Internal COmanage references will automatically be updated as part of upgrading.

New LDAP Provisioner Attributes Supported

v2.0.0 adds support for several new LDAP attributes. In order to enable them, make sure they are defined in your LDAP server's schema. Then edit the appropriate provisioner configuration.

eduPersonAffiliation Fix

Prior to v2.0.0, the LDAP Provisioning Plugin incorrectly localized the eduPersonAffiliation value when exporting it. By default, the localized value is the same as the spec value, so most installations are unlikely to be affected by this change. However, if you were relying on the old (incorrect) behavior, you may need to update your integrations.

Change In Behavior Of LDAP Provisioner

v2.0.0 changes the default way unconfigured (disabled) attributes are handled when provisioning LDAP records. More information is available here.

Clarification of CO Person Role Validity Timezones

Like all other timestamps, CO Person Role valid from and valid through records are stored in UTC. Prior to v2.0.0, this was not made clear via the user interface, and so most likely validity dates were entered in the local timezone.

For example, an administrator in Boston (EST, -0500) enters a valid through timestamp of December 31 23:59:59 and assumes that means EST. However, because Registry operates in UTC, the effective valid through timestamp will be December 31 18:59:59 EST, or 5 hours earlier than the administrator expects.

v2.0.0 automatically converts validity timestamps to and from the browser's detected timezone. However, administrators should be aware that existing records may not be the exact time expected, and may wish to update them accordingly.

COU Changelog Enabled

v2.0.0 enables Changelog Behavior for COUs. As a result of this change, a unique constraint has been removed for the database schema. However, the schema update process may not correctly remove this constraint, and so it may need to be removed manually.

Postgres Example
alter table cm_cous drop constraint cm_cous_co_id_key; 
  • No labels