Enrollment without a name is accepted, but leads to buggy behaviour

XMLWordPrintable

    • Type: Bug
    • Resolution: Unresolved
    • Priority: Minor
    • COmanage Registry Future
    • Affects Version/s: COmanage Registry 3.2.2 (Oyster Pearl MR2)
    • Component/s: Registry
    • None

      Even if the CO configuration states 'a name should always contain at least givenName', if the Name attribute is not available during enrollment, this requirement is not checked. Making Name optional also triggers this behaviour.

      In such cases, an empty name is used for OrgIdentity and COPerson. The person is added to the CO, but does not appear in the 'My Population' list. The COPerson record is available by using the Identity menu and group memberships are correctly registered, although the Person is named ( ? ) at that point.

      Enrollment should enforce some default name if no name is available at the point where a COPerson record is supposed to have been created (after pipelines have run, etc.).

       

            Assignee:
            Benn Oshrin
            Reporter:
            Michiel Uitdehaag (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: