Registry v0.9.2 introduces Extended Types for additional attributes, and changes how Extended Types work for Identifiers (which already supported them). This is a fairly disruptive change and requires the following steps to be run:
- Make sure the database schema has updated successfully. Several fields are made wider. In particular, Postgres databases may need to be manually updated due to CO-165.
- Convert any existing Identifier extended types:
- Instantiate the new default types. This must be done for each CO you have defined, including the COmanage CO.
- Select Collaborations >> CO >> Configuration >> Extended Types
- For each attribute in the For Attribute popup, select the attribute from the popup and then click Add/Restore Default Types.
- Update existing type values for the new types (note multiple formats given for the same commands, so if you run the POSTGRES commands you don't need to run the SQL commands):
- Update existing enrollment flow attributes for the new types:
- If any enrollment flows have an affiliation attribute with a default value, the default value must be re-selected manually (edit the appropriate enrollment flow attribute), even if it appears that the default value is correct.
- For any defined LDAP Provisioners, decide whether or not to provision the
employeeTypeattribute. This must be done regardless of the decision. Edit the appropriate provisioning target(s) and scroll to the list of attributes. Check or uncheck
employeeType, as appropriate. Click Save, whether or not any changes were made.
- For any defined LDAP Provisioners, reselect the types to export for the following attributes. This must be done for any enabled attribute, even if it appears the correct value is already selected:
- If CO Self Service Permissions are defined, they may need to be updated for the new types:
- If any Identifier Assignments are defined with type
cm_co_petition_attributesshould be updated, although this is not strictly necessary. This table holds archived petition attributes – ie their values at time of petition creation. Updating these values will allow them to render correctly via the UI, but no other functionality is otherwise impacted.
Fix Incorrect Foreign Key
Prior versions of the database schema incorrectly created a foreign key from
cm_co_groups:id instead of
cm_cous:id. Running the database schema update should fix this, but it is best to verify this manually.
To manually fix the foreign key (Postgres):
Automated Processing (via cron)
Registry v0.9.2 also introduces cron based automatic processing. Install the cron command to enable this processing.
Add CMP Enrollment Attribute Types
If CMP Enrollment Attributes have been defined (typically for populating organizational identity attributes from authoritative sources), types must be added for many of these attributes:
Also, ePPN is no longer a CMP Enrollment Attribute: