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

UI Glitch when using LDAP Realm with (Project-based) Matrix Authorization Strategy

    • Icon: Bug Bug
    • Resolution: Duplicate
    • Icon: Minor Minor
    • _unsorted
    • None
    • Platform: Other, OS: All

      First my configuration setup (LDAP DIT):

      dn: ou=Admins,ou=Hudson,ou=Applications,dc=example,dc=com
      cn: Admin
      objectClass: groupOfUniqueNames
      objectClass: top
      ou: Admins
      uniqueMember: uid=root,ou=Users,dc=example,dc=com
      uniqueMember: uid=user,ou=Users,dc=example,dc=com

      (I dunno how to include screenshots, so I put them on my webserver)…

      Realm configuration: http://vps01.her.boksa.de/daten/realm.png
      The "glitch": http://vps01.her.boksa.de/daten/glitch.png

      As you can see in the second screenshot the ""-sign implies that the entry is invalid, however it is
      needed for LDAP-groups to function properly. If you need further information just let me know…

        1. glitch.png
          glitch.png
          24 kB
        2. realm.png
          realm.png
          28 kB

          [JENKINS-3872] UI Glitch when using LDAP Realm with (Project-based) Matrix Authorization Strategy

          bboksa added a comment -

          Created an attachment (id=741)
          LDAP realm

          bboksa added a comment - Created an attachment (id=741) LDAP realm

          bboksa added a comment -

          Created an attachment (id=742)
          UI glitch

          bboksa added a comment - Created an attachment (id=742) UI glitch

          Alan Harder added a comment -

          .

              • This issue has been marked as a duplicate of 3459 ***

          Alan Harder added a comment - . This issue has been marked as a duplicate of 3459 ***

            Unassigned Unassigned
            bboksa bboksa
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated:
              Resolved: