Details
-
Type:
New Feature
-
Status: Resolved (View Workflow)
-
Priority:
Major
-
Resolution: Fixed
-
Component/s: embeddable-build-status-plugin
-
Labels:
-
Environment:Matrix-based security
Project-based Matrix Authorization Strategy
-
Similar Issues:
Description
Currently, this plugin requires that the anonymous user has overall Read permissions on Jenkins. If you remove overall Read permission from the anonymous user, this plugin does not work.
If the anonymous user has no Overall Read permissions, but has Job Read permissions, then the icons should still work. But it appears that Jenkins still wants the user to login. This might be a limitation of Jenkins authorization.
Attachments
Issue Links
- duplicates
-
JENKINS-17798 build badge icon requires authentication
-
- Closed
-
Activity
Shawn Baker
created issue -
A user without an overall read access to Jenkins is an user who is not supposed to see anything whatsoever in Jenkins. Letting them see the build status violates the access control model, and as a matter of fact the core doesn't even let us do that in the plugin.
What's the use case for this?
use case: publish public build status from private jenkins
My personal use case is that we have a Jenkins server that is separate from our Trac/Subversion server. Login information is different as well. But both systems are restricted to outside users.
I would like to put the build status on the Trac wiki, but the user who is logged into Trac has different credentials on Jenkins, so the build status icons don't work.
I hope this makes sense.
Shawn Baker
added a comment - My personal use case is that we have a Jenkins server that is separate from our Trac/Subversion server. Login information is different as well. But both systems are restricted to outside users.
I would like to put the build status on the Trac wiki, but the user who is logged into Trac has different credentials on Jenkins, so the build status icons don't work.
I hope this makes sense. My use case, quoted directly from the plugin page
"You can put this URL into other sites (such as GitHub README) so that people can see the current state of the build."
With the restriction, of course, that the project being a private org repo.
Leo Li
added a comment - My use case, quoted directly from the plugin page
"You can put this URL into other sites (such as GitHub README) so that people can see the current state of the build."
With the restriction, of course, that the project being a private org repo. 
Is this fixed by https://issues.jenkins-ci.org/browse/JENKINS-17798 ?
EDIT: I think it did, at least provided a workaround good enough to close this ticket.
Leo Li
added a comment - - edited Is this fixed by https://issues.jenkins-ci.org/browse/JENKINS-17798 ?
EDIT: I think it did, at least provided a workaround good enough to close this ticket. If I understand it correctly, this was fixed in version 1.4.
Marius Gedminas
added a comment - If I understand it correctly, this was fixed in version 1.4. Marius Gedminas
made changes -
| Field | Original Value | New Value |
|---|---|---|
| Link |
This issue duplicates |
If I understand this issue correctly, it was fixed in version 1.4.
Marius Gedminas
added a comment - If I understand this issue correctly, it was fixed in version 1.4. Marius Gedminas
made changes -
| Resolution | Fixed [ 1 ] | |
| Status | Open [ 1 ] | Resolved [ 5 ] |
Sorry to bump this resolved ticket but this is not possible when using "Github Commiter Authorization Strategy"
Behcet Uyar
added a comment - Sorry to bump this resolved ticket but this is not possible when using "Github Commiter Authorization Strategy" | Workflow | JNJira [ 146570 ] | JNJira + In-Review [ 191981 ] |
A very easy workaround would be that instead of having the entrypoint
{JENKINS_URL}/job/{JOB_NAME}/badge/icon redirects to {JENKINS_URL}/static/
{HASH?}/plugin/embeddable-build-status/status/
{STATUS_IMAGE}, why not just generate the image and overwrite to a always fixed image link that is specified by the admin of the job/Jenkins server.