[JIRA] [role-strategy-plugin] (JENKINS-34545) Assigning roles is case sensitive, and it shouldn't be

2 views
Skip to first unread message

chris.and.amy.shannon@gmail.com (JIRA)

unread,
May 2, 2016, 5:08:01 PM5/2/16
to jenkinsc...@googlegroups.com
Christopher Shannon created an issue
 
Jenkins / Bug JENKINS-34545
Assigning roles is case sensitive, and it shouldn't be
Issue Type: Bug Bug
Assignee: Oleg Nenashev
Components: role-strategy-plugin
Created: 2016/May/02 9:07 PM
Environment: Jenkins 1.646
Role-based Authorization Strategy 2.2.0
Labels: plugin plugins security
Priority: Minor Minor
Reporter: Christopher Shannon

Steps to reproduce:

  1. Create a user in Jenkins own user database with upper-case letters.
  2. Assign a role to this user, but use lower-case letters.
  3. Note that going back into Assign Roles shows the icon indicating that this user is valid.
  4. Note that this user does not have the appropriate role.
  5. Remove the previous role and assign the role to the user using upper-case letters.
  6. Note that the user now has the appropriate role.

Since a user can login to their account in a case insensitive way, the role assignments should also be handled in a case insensitive way. Right now, it is very hard to figure out why roles are not working when the case is not matched between the role screen and the user database.

Add Comment Add Comment
 
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
Atlassian logo

David.W.Wise@mac.com (JIRA)

unread,
Feb 6, 2017, 12:39:02 PM2/6/17
to jenkinsc...@googlegroups.com
David Wise commented on Bug JENKINS-34545
 
Re: Assigning roles is case sensitive, and it shouldn't be

I have the same issue. My Jenkins instance uses Security Realm of Active Directory, and Authorization of Role-Based Strategy. If the user does not use the same user ID case I use in Role Strategy, then they get the _missing the Overall/Read permission _error.

As Active Directory does not care about case, my *workaround *is to enter 2 global and project entries for the user. One uppercase, DW12345, and one lowercase, dw12345. I could tell the user to use only lowercase, but then I would just get hassled by users who don't remember, or want an excuse to debate why we are moving to Jenkins. Love the plugin, as it works perfectly to control job visibility and read/write permissions. But the case sensitivity is an unnecessary pain.

This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
Atlassian logo

David.W.Wise@mac.com (JIRA)

unread,
Feb 6, 2017, 12:43:04 PM2/6/17
to jenkinsc...@googlegroups.com
David Wise edited a comment on Bug JENKINS-34545
I have the same issue.  My Jenkins instance uses Security Realm of Active Directory, and Authorization of Role-Based Strategy.  If the user does not use the same user ID case I use in Role Strategy, then they get the _missing "missing the Overall/Read permission _error " error .  

As Active Directory does not care about case, my
*workaround * WORKAROUND is to enter 2 global and project entries for the user.  One uppercase, DW12345, and one lowercase, dw12345.  I could tell the user to use only lowercase, but then I would just get hassled by users who don't remember, or want an excuse to debate why we are moving to Jenkins.  Love the plugin, as it works perfectly to control job visibility and read/write permissions.  But the case sensitivity is an unnecessary pain.

o.v.nenashev@gmail.com (JIRA)

unread,
Sep 16, 2018, 7:32:02 AM9/16/18
to jenkinsc...@googlegroups.com
Oleg Nenashev updated an issue
 
Jenkins / New Feature JENKINS-34545
Change By: Oleg Nenashev
Issue Type: Bug New Feature
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)

o.v.nenashev@gmail.com (JIRA)

unread,
Sep 16, 2018, 7:35:02 AM9/16/18
to jenkinsc...@googlegroups.com

o.v.nenashev@gmail.com (JIRA)

unread,
Dec 25, 2018, 4:46:10 AM12/25/18
to jenkinsc...@googlegroups.com
Oleg Nenashev assigned an issue to Unassigned
 

Unassigning the issue for now. We have added two Role Strategy plugin project ideas to GSoC 2019: https://jenkins.io/projects/gsoc/2019/project-ideas/. If somebody is interested in co-mentoring the ideas (including these tickets), please let us know

Change By: Oleg Nenashev
Assignee: Oleg Nenashev

Daniel.Pasto@gmail.com (JIRA)

unread,
Aug 7, 2019, 10:45:02 AM8/7/19
to jenkinsc...@googlegroups.com
D Pasto commented on New Feature JENKINS-34545
 
Re: Assigning roles is case sensitive, and it shouldn't be

I verified the workaround of assigning the user multiple times to each role:  JoeUser, joeuser, Joeuser, JOEUSER

It doesn't display right since the LDAP lookup doesn't like the duplication, and it wouldn't scale well, but it does work - I can login with the most common capitalization patterns and get the right permissions

Reply all
Reply to author
Forward
0 new messages