Folder-based Authorization Strategy
The Jenkins project announced an unresolved security vulnerability affecting the current version of this plugin (
why?):
List of issuesKey | Summary | Created | Updated |
---|
JENKINS-74903 | Changing to a new authentication configuration erased existing configuration | | |
---|
JENKINS-72511 | Folder auth plugin multiple SID input ambiguity. | | |
---|
JENKINS-72433 | Can not add role in Jenkins 2.426.1 with folder auth plugin because Prototype.js is used in folder auth plugin | | |
---|
JENKINS-70753 | Assign no permissions to read in a folder or other subfolder but in a subfolder build and read | | |
---|
JENKINS-67943 | Do not differ between upper / lower case in SID | | |
---|
JENKINS-62443 | Use the user's Full Name on the role page if set | | |
---|
JENKINS-62318 | X button on recent Jenkins ~2.236 styles broken | | |
---|
JENKINS-62296 | Remove 'X' for admin role | | |
---|
JENKINS-62287 | SID naming | | |
---|
JENKINS-62286 | Add a global read role | | |
---|
JENKINS-62284 | Increase the default size of select boxes | | |
---|
JENKINS-62283 | Folder auth support for System read | | |
---|
JENKINS-62236 | add/remove folders to the existing roles and add/remove multiple users at one time | | |
---|
JENKINS-59105 | Accessing Jenkins using API token does not work in group memberships | | |
---|