|
||||||||
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-9142) "Add Build Ste... dogf...@java.net (JIRA)
- [JIRA] (JENKINS-9142) "Add Buil... co...@colinharrington.net (JIRA)
- [JIRA] (JENKINS-9142) "Add Buil... co...@colinharrington.net (JIRA)
- [JIRA] (JENKINS-9142) "Add Buil... wbucks...@gmail.com (JIRA)
- [JIRA] (JENKINS-9142) "Add Buil... jsamp...@namemedia.com (JIRA)
- [JIRA] (JENKINS-9142) "Add Buil... jsamp...@namemedia.com (JIRA)
- [JIRA] (JENKINS-9142) "Add Buil... dan.lat...@glooware.com (JIRA)
- [JIRA] (JENKINS-9142) "Add Buil... dan.lat...@glooware.com (JIRA)
- [JIRA] (JENKINS-9142) "Add Buil... dan.lat...@glooware.com (JIRA)
Does seem to be some kind of securities issue in our case; Crowd and LDAP plugins installed, currently set to authenticate to Active Directory, logging in seems to make the issue go away. We have things set to 'Anyone can do anything', but in the case of these AJAX requests, perhaps 'anything' isn't quite that global?