That behavior...I don't remember seeing. Sorry. --Rob
From: jenkinsci-users@googlegroups.com [mailto:jenkinsci-users@googlegroups.com] On Behalf Of Merrow, Frank Sent: Wednesday, November 14, 2012 11:47 AM To: jenkinsci-users@googlegroups.com Cc: fmer...@san.rr.com (fmer...@san.rr.com) Subject: RE: Problems with "Authorization" configuration . . . Rob, I just updated a system that I have not applied "the fix" to . . . to Jenkins 1.490. The results are mixed . . . The good news (great news in fact) is that the "login" ICON does now appear . . . so users can login . . . The bad news is that all Job ICONs remain broken . . . Anonymous users still cannot see job status . . . and yes I double checked . . . Anonymous has all three "read" permissions. Frank From: jenkinsci-users@googlegroups.com<mailto:jenkinsci-users@googlegroups.com> [mailto:jenkinsci-users@googlegroups.com]<mailto:[mailto:jenkinsci-users@googlegroups.com]> On Behalf Of Mandeville, Rob Sent: Tuesday, November 13, 2012 6:13 AM To: jenkinsci-users@googlegroups.com<mailto:jenkinsci-users@googlegroups.com> Cc: fmer...@san.rr.com<mailto:fmer...@san.rr.com> (fmer...@san.rr.com<mailto:fmer...@san.rr.com>) Subject: RE: Problems with "Authorization" configuration . . . I can't find the issue number or the part of the change log that speaks to it, but I've had this problem. This was fixed in the past couple of months (somewhere...), so upgrading Jenkins will fix this, if you're willing to do "Latest and Greatest" rather than long-term support release. --Rob From: jenkinsci-users@googlegroups.com<mailto:jenkinsci-users@googlegroups.com> [mailto:jenkinsci-users@googlegroups.com] On Behalf Of Merrow, Frank Sent: Monday, November 12, 2012 7:36 PM To: jenkinsci-users@googlegroups.com<mailto:jenkinsci-users@googlegroups.com> Cc: fmer...@san.rr.com<mailto:fmer...@san.rr.com> (fmer...@san.rr.com<mailto:fmer...@san.rr.com>) Subject: Problems with "Authorization" configuration . . . We have a number of Jenkins here and I've seen this issue repeatedly . . . I have seen this issue BOTH with "Logged-in users can do anything" and I have also seen it with "Project-based Matrix Authorization Strategy" where "Anonymous" has Overall/Read, Job/Read and View/Read. The issue is that a logged out user see's broken ICONS (logged in users work fine): [cid:image001.png@01CDC0EF.E85D7C90] While annoying, the really hard part for user's to deal with is that additionally, in this mode, the login button disappears: [cid:image002.png@01CDC0EF.E85D7C90] The login button is there and if you blindly stab at it you can bring up the login screen . . . but that isn't an obvious choice for first time users. Ah, but there is more . . . I have a work around, but it makes no sense . . . Since I didn't see anything like this in the Jenkins JIRA tickets, I figured I just had things configured incorrectly, so one day I sat down and started turning on Matrix options to Anonymous one-by-one . . . I figured eventually I'd find the right combination that would make it work. I started from the right, added a permission, logged out, logged in, then added another permission, logged out . . . kept doing this until it worked . . . This problem was that the ICONs didn't work "logged out" unless I gave Anonymous "Admin" . . . clearly not a good choice. HOWEVER, the really odd thing was that once I gave Anonymous Admin, I could take AWAY everything except the three Read permissions (the ones I started with) and it would continue to work! (???) So that is what I've done to "fix" around 10 systems now . . . I give Anonymous Admin, log out, log in and take it away . . . from then on it works fine. The really odd thing is that this solution even works for "Logged-in users can do anything" . . . except in that case I have to convert to Project Matrix . . . give Anonymous Admin, take it away and then go back to "Logged-in users can do anything" . . . if fix will remain fixed. It is nice that I have a work around . . . but I just cannot figure out why is happens and since I don't see anything in Jenkins JIRA, why does it only seem to happen here? Any ideas? Frank P.S. As a side issue . . . we WANT user's to be able to see the status of jobs before they log in if they want too . . . another "work around" is to just remove the three Read Permissions from Anonymous. In this case, the user sees ONLY a login screen and that works fine except it doesn't allow them to see anything . . . we WANT them to be able to look at their jobs without logging in. P.S.S. For those who might responsed this is a browser caching issue . . . I've tested all of that . . . clearing the cache will NOT fix the issue. The information in this message is for the intended recipient(s) only and may be the proprietary and/or confidential property of Litle & Co., LLC, and thus protected from disclosure. If you are not the intended recipient(s), or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any use, dissemination, distribution or copying of this communication is prohibited. If you have received this communication in error, please notify Litle & Co. immediately by replying to this message and then promptly deleting it and your reply permanently from your computer.
<<inline: image001.png>>
<<inline: image002.png>>
