Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-32711

Adding Co-Owners by "Display Name" does not work

    • Icon: Improvement Improvement
    • Resolution: Unresolved
    • Icon: Minor Minor
    • ownership-plugin
    • None
    • Jenkins 1.625 LTS, Ownership Plugin .7 Active Directory Plugin 1.41

      We recently had an issue wherein a job owner added a co-owner by entering their display name ("LName, FName" in our case). This appeared to work. The co-owner was correctly displayed on the ownership page, including resolution of their email address. However the co-owner did not acquire the permissions that a co-owner should receive. They were unable to view or edit the job configuration for example. When we removed them and re-added them as "fname.lname", which is their active directory login, (we use the "Active Directory" security realm) things worked. It seems that either both approaches should work (probably not the best solution as display name can be ambiguous) or there needs to be a clear error or other indicator when a non-valid user-id is entered as a co-owner.

          [JENKINS-32711] Adding Co-Owners by "Display Name" does not work

          Kenneth Baltrinic created issue -
          Kenneth Baltrinic made changes -
          Description Original: We recently had an issue wherein a job owner added a co-owner by entering their display name "LName, FName" in our case. This appeared to work. The co-owner was correctly displayed on the ownership page, including resolution of their email address. However the co-owner did not acquire the permissions that a co-owner should receive. They were still unable to view or edit the job configuration for example. When we removed them and re-added them as "fname.lname", which is their active directory login, (we use the "Active Directory" security realm) things worked. It seems that either both approaches should work (probably not the best solution as display name can be ambiguous) or there needs to be a clear error or other indicator when a non-valid user-id is entered as a co-owner.

          New: We recently had an issue wherein a job owner added a co-owner by entering their display name ("LName, FName" in our case). This appeared to work. The co-owner was correctly displayed on the ownership page, including resolution of their email address. However the co-owner did not acquire the permissions that a co-owner should receive. They were unable to view or edit the job configuration for example. When we removed them and re-added them as "fname.lname", which is their active directory login, (we use the "Active Directory" security realm) things worked. It seems that either both approaches should work (probably not the best solution as display name can be ambiguous) or there needs to be a clear error or other indicator when a non-valid user-id is entered as a co-owner.

          Oleg Nenashev made changes -
          Attachment New: Screen Shot 2016-02-01 at 23.48.18.png [ 31732 ]
          Oleg Nenashev made changes -
          Issue Type Original: Bug [ 1 ] New: Improvement [ 4 ]
          R. Tyler Croy made changes -
          Workflow Original: JNJira [ 168373 ] New: JNJira + In-Review [ 183091 ]
          Oleg Nenashev made changes -
          Assignee Original: Oleg Nenashev [ oleg_nenashev ]
          Oleg Nenashev made changes -
          Labels Original: AD New: AD newbie-friendly
          Mark Waite made changes -
          Labels Original: AD newbie-friendly

            Unassigned Unassigned
            kbaltrinic Kenneth Baltrinic
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: