Page History

Because Registry Enrollment may involve subjects without existing Registry records, authentication and authorization for Registry Enrollment Flows operates a bit differently than for the rest of Registry or other parts of the COmanage Platform. Registry Enrollment can involve multiple steps by various actors, which can be interrupted and re-engaged at various times.

...

• If Enrollment Authorization is configured (ie: not None), then the Petitioner is an existing CO Person. The Petitioner's CO Person ID is recorded is part of the Petition artifact.
• If Enrollment Authorization is not configured (ie: set to None), then the Enrollment Flow is open, and the Petitioner may not be an existing CO Person. A random token will be is generated to link the Petitioner steps.

...

1. A Platform Administrator, CO Administrator, or COU Administrator (when the Petitioner is in the population of the COU Administrator) may execute the step. This is not always advisable, as depending on the configuration incorrect attributes (those of the Administrator rather than those of the Petitioner) may be collected.
2. If a Petitioner CO Person ID was recorded and the currently authenticated user has the same CO Person ID, the current user may execute the step.
3. If the Petitioner presents a valid token, the they may resume the associated Petition.

...

1. A Platform Administrator, CO Administrator, or COU Administrator (when the Enrollee is in the population of the COU Administrator) may execute the step. This is not always advisable, as depending on the configuration incorrect attributes (those of the Administrator rather than those of the Enrollee) may be collected.
2. If an Enrollee CO Person ID was recorded and the currently authenticated user has the same CO Person ID, the current user may execute the step.
3. If the Enrollee presents a valid token, the they may resume the associated Petition.

...