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

Support case-insensitive mode for user IDs

    XMLWordPrintable

Details

    Description

      We use this plugin with Active Directory users authorisation and via AD user can be authorised with lowercase and CamelCase names. But "role-strategy" plugin uses exact user name and we have to register two user names for each user - lowercase and CamelCase.

      Attachments

        Issue Links

          is duplicated by

          Bug - A problem which impairs or prevents the functions of the product. JENKINS-68077 Uppercased user name failed to assign role

          • Major - Major loss of function.
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. JENKINS-55111 Case sensitivity issue between LDAP plugin and role-strategy plugin when using Active Directory and using API tokens

          • Minor - Minor loss of function, or other problem where easy workaround is present.
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. JENKINS-70467 Assign Global Roles case sensitive issues

          • Minor - Minor loss of function, or other problem where easy workaround is present.
          • Closed

          New Feature - A new feature of the product, which has yet to be developed. JENKINS-20340 Allow case insensitive user matching

          • Major - Major loss of function.
          • Closed

          New Feature - A new feature of the product, which has yet to be developed. JENKINS-34545 Assigning roles is case sensitive, and it shouldn't be

          • Minor - Minor loss of function, or other problem where easy workaround is present.
          • Closed
          is related to

          Bug - A problem which impairs or prevents the functions of the product. JENKINS-12607 Active directory user names should not be case sensitive.

          • Blocker - Blocks development and/or testing work, production could not run.
          • Open

          New Feature - A new feature of the product, which has yet to be developed. JENKINS-19320 Add support of user macros

          • Major - Major loss of function.
          • Open
          relates to

          New Feature - A new feature of the product, which has yet to be developed. JENKINS-22247 Provide an extension point to define user id case sensitivity contract

          • Major - Major loss of function.
          • Resolved

          Activity

            Ascending order - Click to sort in descending order
            oleg_nenashev Oleg Nenashev added a comment -

            Issue is caused by active-directory plugin

            oleg_nenashev Oleg Nenashev added a comment - Issue is caused by active-directory plugin
            oleg_nenashev Oleg Nenashev added a comment - - edited

            https://issues.jenkins-ci.org/browse/JENKINS-19320 can resolve this issue for role-strategy plugin.
            I'm going to implement such feature at the October

            oleg_nenashev Oleg Nenashev added a comment - - edited https://issues.jenkins-ci.org/browse/JENKINS-19320 can resolve this issue for role-strategy plugin. I'm going to implement such feature at the October
            oleg_nenashev Oleg Nenashev added a comment -

            Pull request: https://github.com/jenkinsci/role-strategy-plugin/pull/5
            You can find test hpi in attachments

            oleg_nenashev Oleg Nenashev added a comment - Pull request: https://github.com/jenkinsci/role-strategy-plugin/pull/5 You can find test hpi in attachments
            oleg_nenashev Oleg Nenashev added a comment -

            Attached hpi with a fix

            oleg_nenashev Oleg Nenashev added a comment - Attached hpi with a fix
            oleg_nenashev Oleg Nenashev added a comment -

            Alexey, please test the plugin against ActiveDirectory. It works well for me (LDAP and LocalDatabase)

            oleg_nenashev Oleg Nenashev added a comment - Alexey, please test the plugin against ActiveDirectory. It works well for me (LDAP and LocalDatabase)
            oleg_nenashev Oleg Nenashev added a comment -

            Global configuration example

            oleg_nenashev Oleg Nenashev added a comment - Global configuration example
            waltern Walter Nagler added a comment -

            Works for me, too.
            In combination with Active Directory plugin

            waltern Walter Nagler added a comment - Works for me, too. In combination with Active Directory plugin
            batmat Baptiste Mathus added a comment -

            +1. IMO this would be better to not mark this issue as fixed for communication, since the code has actually not reached master (still in the PR).

            batmat Baptiste Mathus added a comment - +1. IMO this would be better to not mark this issue as fixed for communication, since the code has actually not reached master (still in the PR).
            oleg_nenashev Oleg Nenashev added a comment -

            batmat, I've reopened the issue.

            I'll consider the merge of the PR in the next release.

            oleg_nenashev Oleg Nenashev added a comment - batmat , I've reopened the issue. I'll consider the merge of the PR in the next release.
            batmat Baptiste Mathus added a comment - - edited

            oleg_nenashev Great! Thanks!

            batmat Baptiste Mathus added a comment - - edited oleg_nenashev Great! Thanks!
            pixman20 pixman20 added a comment - - edited

            Has this been verified to work when using the "authenticated" special "user" when assigning roles.
            It may be that it works inherently, but I just want to verify prior to release.
            Also, will the update provide an option or will it automatically be case insensitive? (n/m, just saw the png)

            pixman20 pixman20 added a comment - - edited Has this been verified to work when using the "authenticated" special "user" when assigning roles. It may be that it works inherently, but I just want to verify prior to release. Also, will the update provide an option or will it automatically be case insensitive? (n/m, just saw the png)
            oleg_nenashev Oleg Nenashev added a comment -

            @pixman20
            Yes, it should work with the "authenticated" user group.
            If you want to perform an additional testing, I can provide the plugin's build with the patch. Such contribution will be appreciated.

            oleg_nenashev Oleg Nenashev added a comment - @ pixman20 Yes, it should work with the "authenticated" user group. If you want to perform an additional testing, I can provide the plugin's build with the patch. Such contribution will be appreciated.
            pixman20 pixman20 added a comment - - edited

            oleg_nenashev, I'd be happy to contribute and test it out. Feel free to email me (address in profile) unless there's somewhere I can grab it from. Thanks!

            pixman20 pixman20 added a comment - - edited oleg_nenashev , I'd be happy to contribute and test it out. Feel free to email me (address in profile) unless there's somewhere I can grab it from. Thanks!
            bherfurth Ben Herfurth added a comment -

            What about the merge?

            bherfurth Ben Herfurth added a comment - What about the merge?
            fsteff Flemming Steffensen added a comment -

            Believe I'm seeing this problem.

            Users will be granted different access, whether they are logging in as lower-case "username" or have any or all letters capitalized.

            If there's still something that needs to be tested prior to merge, please contact me - I'd be happy to test.

            fsteff Flemming Steffensen added a comment - Believe I'm seeing this problem. Users will be granted different access, whether they are logging in as lower-case "username" or have any or all letters capitalized. If there's still something that needs to be tested prior to merge, please contact me - I'd be happy to test.
            oleg_nenashev Oleg Nenashev added a comment -

            I will add it to the scope of https://jenkins.io/projects/gsoc/2019/project-ideas/role-strategy-ux/

            oleg_nenashev Oleg Nenashev added a comment - I will add it to the scope of https://jenkins.io/projects/gsoc/2019/project-ideas/role-strategy-ux/
            oleg_nenashev Oleg Nenashev added a comment -

            I believe that a proper implementation nowadays would be an integration with User ID strategies from JENKINS-22247: https://javadoc.jenkins.io/jenkins/model/IdStrategy.html. Such extension point is available in recent versions

            oleg_nenashev Oleg Nenashev added a comment - I believe that a proper implementation nowadays would be an integration with User ID strategies from  JENKINS-22247 : https://javadoc.jenkins.io/jenkins/model/IdStrategy.html . Such extension point is available in recent versions
            bwaters_sevone brendan waters added a comment -

            I have this same issue with OpenID connect authentication due to camelcase email addresses.  An option to treat all usernames as lowercase would address the issue blocking us from using role based strategy with openID connect

            bwaters_sevone brendan waters added a comment - I have this same issue with OpenID connect authentication due to camelcase email addresses.  An option to treat all usernames as lowercase would address the issue blocking us from using role based strategy with openID connect

            People

              Unassigned Unassigned
              msavich Alex
              Votes:
              17 Vote for this issue
              Watchers:
              20 Start watching this issue

              Dates

                Created:
                Updated: