[
https://issues.jenkins-ci.org/browse/JENKINS-13429?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=162664#comment-162664
]
Brenna Flood commented on JENKINS-13429:
----------------------------------------
Upgraded from 1.458 to 1.463 yesterday and started experiencing this issue.
It's fairly important in our company implementation that anonymous users be
able to continue to browse through nested views without requiring
authentication; for security purposes, the workaround of giving configure
perms for View for anonymous is not viable.
> 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
