|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
- [JIRA] (JENKINS-15309) NPE (isEmpty) from ... [email protected] (JIRA)
- [JIRA] (JENKINS-15309) NPE (isEmpty) ... [email protected] (JIRA)
- [JIRA] (JENKINS-15309) NPE (isEmpty) ... [email protected] (JIRA)
- [JIRA] (JENKINS-15309) NPE (isEmpty) ... [email protected] (JIRA)
- [JIRA] (JENKINS-15309) NPE (isEmpty) ... [email protected] (JIRA)
- [JIRA] (JENKINS-15309) NPE (isEmpty) ... [email protected] (JIRA)
- [JIRA] (JENKINS-15309) NPE (isEmpty) ... [email protected] (JIRA)

I've seen this happen when Anonymous was granted only the OVERALL: Read & JOB:discover permission
Selecting both JOB: READ & DISCOVER permissions resolved the issue or removing the discover altogether also resolved it (but then users get the 404 error when accessing a job from a URL)
(Project-based Matrix Authorization Strategy)