Uploaded image for project: 'COmanage'
  1. COmanage
  2. CO-1782

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

    XMLWordPrintable

    Details

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

      Description

      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.).

       

        Smart Checklist

          Attachments

            Issue Links

              Activity

                People

                Assignee:
                benn.oshrin@at.internet2.edu Benn Oshrin
                Reporter:
                michiel.uitdehaag@at.internet2.edu Michiel Uitdehaag
                Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                  Dates

                  Created:
                  Updated: