-
Bug
-
Resolution: Unresolved
-
Major
-
None
-
Ubuntu, Jenkins 2.138.3 core and libraries
The "Discover" role is to allow the users to know that a resource exists in Jenkins. If the Anonymous User doesn't have "Read" role and have "Discover", they are asked to login.
During a pipeline it is specially useful during a input step. If the Anonymous user has the "Read" role, the step fail after the Ok button is clicked. If it doesn't have, he gets a 404 error and thinks there is an error.
The "Discover permission" does not work while in Blue Ocean. If the Anonymous User has the role Discover but not the Read role, both the main job page and the input page give a 404 Not Found error. Here are the failing urls of the job "teste-aprovador":
http://vrt1071:8280/blue/organizations/jenkins/teste-aprovador/activity/
http://vrt1071:8280/blue/organizations/jenkins/teste-aprovador/detail/teste-aprovador/103/pipeline/
If I go to the old interface and go to the "Paused for input" build link:
http://vrt1071:8280/job/teste-aprovador/104/input/
Jenkins correctly asks me to login so I can see the page.
Here is the sample configuration:
- is related to
-
JENKINS-65589 When not logged in blueocean urls return a 404.
-
- Resolved
-
I seem to be facing the same thing here: https://issues.jenkins.io/browse/JENKINS-65589. I thought adding the DISCOVER permission would fix it, but it doesn't seem that Blueocean respects it!