Sure michaelneale
Reproduction:
- docker run --net=host jenkins/jenkins:lts
- go in manage plugin and install blueocean
- activate "Project-based Matrix Authorization Strategy" in global security and give all the rights to anonymous
- create two folders "test1" and "test2"
- in "test1", activate "Enable project-based security" and give all the rights no anonymous
- in "test2", activate "Enable project-based security", give all the rights no anonymous, and block inheritance
Result:
- you see the "Open Blue Ocean" link on the left menu of test1
- you can't see the "Open Blue Ocean" link on the left menu of test2
Expected:
- The "Open Blue Ocean" link should also appear in test2
I looked into the blue-ocean-rest-impl plugin. There doesn't seem to be any logic that decide if the link should be shown or hidden.
I added log traces in the folder plugin and it looks like the Actions is there even when it's not displayed.
I don't know Jenkins very well, but I think it could be in the matrix-authorization-plugin.
Fyi, with the matrix-authorization-plugin 2.0-beta-4 the link is also displayed when the inheritance is blocked, but it could also be that the plugin is broken (haven't tested it deeply)
We can also reproduce this issue. Here are some additional information
Activating "Block inheritance of global authorization matrix" on a Github Organization or folder will make the "Open Blue Ocean" button disappear from the left menu, even if you give all possible permissions to your user, group, or even anonymous.