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

Role assignments are case sensitive to login credentials

    • Icon: Bug Bug
    • Resolution: Duplicate
    • Icon: Major Major
    • role-strategy-plugin
    • Windows 7 Professional 64bit
      Jenkins 2.19.4
      Role-based Authorization Strategy 2.3.2

      Depending on how you login to Jenkins, the role assignment works or doesn't work.

      e.g. if you assign "simpleuser" a role, but he logs in as "SimpleUser", the role is not assigned. Same with the other way round.

      If the logs out, and logs back in as "simpleuser", it works.

      On his /users/simpleuser page, the "Jenkins login name" is, regardless of how he logs in, stated as "simpleuser".

          [JENKINS-40442] Role assignments are case sensitive to login credentials

          Jan Vodolan added a comment -

          Unfortunatelly, I can confirm such behavior...

          LDAP users in camel: UserName
          Jenkins role management accepts lower case: username (this user is validated as existing)
          It is possible to log as: UserName, but this use has no roles assigned
          It is also possible to log as: username, this time user has roles assigned and everything is working.

          So, LDAP is case insensitive, but role strategy plugin is case sensitive.

          Jan Vodolan added a comment - Unfortunatelly, I can confirm such behavior... LDAP users in camel: UserName Jenkins role management accepts lower case: username (this user is validated as existing) It is possible to log as: UserName, but this use has no roles assigned It is also possible to log as: username, this time user has roles assigned and everything is working. So, LDAP is case insensitive, but role strategy plugin is case sensitive.

            oleg_nenashev Oleg Nenashev
            flopes Florian Peschka
            Votes:
            1 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: