Versions Compared

Key

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

...

  • Manually, via People >> Organizational Identities >> Add New Org Identity From Source or by using the Search button from the list of Organizational Identity Sources.
  • Using an Enrollment Flow, via Enrollment Sources.
  • Via a batch process. (Not yet implemented; CO-76)the Registry Job Shell syncorgsources task, as described below.

Organizational Identity Sources can be linked to Registry Pipelines in order to automatically create CO Person records.

...

  • View Organizational Identity: Retrieves the current Org Identity operational record used by Registry in normal operations.
  • View Organizational Identity Source: Performs a live query against the Org Identity Source backend and retrieves the current data as known to the backend. ie: This is the source's current data.
  • View Organizational Identity Source Record: Retrieves the last data retrieved from the backend and used to create or update an Org Identity. ie: This is Registry's copy of the source data.
  • Add New Org Identity From Source: Create a new Org Identity based on the Org Identity Source's data. In addition, this will create an Organizational Identity Source Record.
  • Resync Org Identity From Source: Update the Org Identity and Organizational Identity Source Record using the latest (current) data available from the Org Identity Source.
  • Configuration >> Organizational Identity Sources: Manage the plugins used to define and query one or more Org Identity Sources.

Sync Modes

 When When called from Registry Job Shell via the syncorgsources task, Organizational Identity Sources can be configured in the following sync modes:

...

An ePPN will not be generated if one is found in the Org Identity record created from the Source.

CO Group Mappings

Organizational Identity Sources can generate CO Group Memberships via Group Mappings, when the relevant OIS Plugin implements the appropriate interfaces. However, since group memberships attach to a CO Person and not an Organizational Identity, for this to be useful the OIS must typically be attached to a Pipeline, which will then create CO Group Memberships attached to the relevant CO Person record. For OIS Plugins that support this feature, the steps to enable it are:

  1. Make sure the group(s) you want to add memberships to already exists. Automatic groups (such as members groups) cannot be used here.
  2. View the OIS configuration (ie: use the Edit button, not the Configure button), and click Configure Group Mapping.
    1. (info) In Registry versions prior to v3.1.0, the Configure Group Mapping button is available on the index page of Organizational Identity Sources.
    2. The OIS must be connected to a Pipeline for CO Group Memberships to be assigned.
  3. Add one or more mappings.
    1. Attribute: The attribute found in the Organizational Identity Source.
    2. Target Group: The group for which a membership will be created, when the Org Identity has an Attribute matching the specified Comparison and Pattern.
  4. At this point, if you search the Organizational Identity Source, any records matching the defined mappings will also show what CO Group memberships would be assigned if a CO Person record were created from or attached to this source record. However, an action triggering the Pipeline (as described above) must take place