...
- Advisory matching is configured for the enrollment flow.
- The field where data is entered is either a given or family name field.
If an enrollment flow is configured to collect more than one type of name, only the first set of name fields emitted will be enabled for Advisory Matching. - At least 3 characters are entered into the field.
Organizational Identity Sources
Enrollment Flows can be configured to query Organizational Identity Sources for Organizational Identity data. Such enrollments will result in new Org Identities created, linked to the specified Organizational Identity Source. How this happens depends on who the Petitioner is.
- If the Petitioner is any type of administrator, the Petitioner will be able to select any Organizational Identity Source, query it, and select any record that is not already linked to an Org Identity.
- If the Petitioner is authenticated, but not an administrator, the Petitioner will be asked for an email address, and then to verify control over that email address by entering a code sent to it. All Organizational Identity Sources will be queried for that email address, and if any return matching records the Petitioner will be able to select one to use as part of the enrollment.
- Unauthenticated Petitioners may not query Organizational Identity Sources.
To enable this capability, set the Org Identity Mode for the Enrollment Flow to Org Identity Source. Additional modes may be added in future releases.
Duplicate Enrollments
COmanage Registry can detect duplicate enrollments under limited circumstances. (Alternately, duplicates can be manually resolved.) When enrollee authentication is required (see below), the authenticated identifier is used to check for prior enrollments. What happens when a duplicate enrollment is detected is configurable on a per-Enrollment Flow basis:
...