[
https://issues.jenkins-ci.org/browse/JENKINS-13429?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=163099#comment-163099
]
SCM/JIRA link daemon commented on JENKINS-13429:
------------------------------------------------
Code changed in jenkins
User: Vincent Latombe
Path:
changelog.html
core/src/main/java/hudson/security/AuthorizationStrategy.java
http://jenkins-ci.org/commit/jenkins/d1b2ba7e4988d26fbb815b8912efb16273c407d4
Log:
[FIXED JENKINS-13429]
Backward compatibility is preventing the View.READ permission to apply
correctly. It actually overrides the View.READ instead of complementing
it.
This change only applies default READ right if the View.READ is not
available, and the user has View.CONFIGURE + the view is not empty.
> Nested views not showing up with just read perms for View
> ---------------------------------------------------------
>
> Key: JENKINS-13429
> URL: https://issues.jenkins-ci.org/browse/JENKINS-13429
> Project: Jenkins
> Issue Type: Bug
> Components: nested-view
> Affects Versions: current
> Reporter: M S
> Assignee: Kohsuke Kawaguchi
> Labels: jenkins, plugin, views
>
> Jenkins 1.459 + Nested View Plugin 1.8 + Role-based Authorization Strategy
> 1.1.2
> User has read permissions for "View" but Jenkins main page is missing Nested
> views (even if they have sub views with jobs).
> Adding "configure" perms for "View" results in Nested views showing up
> correctly.
> It looks like it's connected with:
> "Added the View.READ permission to control visibility of views, and updated
> the default implementation to hide empty views. (issue 3681)"
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
