[JIRA] [core] (JENKINS-22409) API Token no longer working for API calls
Justin Zaun commented on JENKINS-22409 API Token no longer working for API calls I've downgraded back to jenkins 1.550 and the API Token starts working again. I hope I'm not stuck on v1.550 forever. 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 -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-22409) API Token no longer working for API calls
Justin Zaun commented on JENKINS-22409 API Token no longer working for API calls I've tried version "0.15-SNAPSHOT (private-03/05/2014 10:52-soren)" of the github-oauth plugin as well from https://github.com/sorenh/github-oauth-plugin/releases and it doesn't fix the issue, APT Token still not working. 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 -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-22409) API Token no longer working for API calls
Justin Zaun created JENKINS-22409 API Token no longer working for API calls Issue Type: Bug Affects Versions: current Assignee: Sam Kottler Components: core, github-oauth, security Created: 28/Mar/14 6:00 PM Description: All our API calls are now failing. Even a simple thing like this: :@jenkins.goonies3.com/api/json I keep getting: Error 401 Unexpected authentication type: org.acegisecurity.providers.UsernamePasswordAuthenticationToken@b69dc627: Username: ; Password: [PROTECTED]; Authenticated: false; Details: org.acegisecurity.ui.WebAuthenticationDetails@8868: RemoteIpAddress: ; SessionId: null; Not granted any authorities How do I get my API calls working again? This is a huge issue, it's brining most of our automated processing to a halt. Environment: Jenins: 1.556 github-oauth: 0.14 Project: Jenkins Priority: Critical Reporter: Justin Zaun 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 -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [github-oauth] (JENKINS-20845) Github Authorization Settings, users in "Participant in Organization" not given READ
Justin Zaun created JENKINS-20845 Github Authorization Settings, users in "Participant in Organization" not given READ Issue Type: Bug Affects Versions: current Assignee: Sam Kottler Components: github-oauth Created: 02/Dec/13 10:57 PM Description: We have an organization setup with all our users as members. Most of our repositories are private. I can see the "Participant in Organization" gives the additional permissions but it doesn't give the basic READ permission. This means I have to check "Grant READ permissions to all Authenticated Users" so users also get READ. The thing is we don't want any old user to have READ, only people in the organization. Environment: Jenkins ver. 1.541 Github Authentication plugin 0.14 Project: Jenkins Priority: Major Reporter: Justin Zaun 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 -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-11547) Jobs trigger continually even though there are no changes due to git repository being "corrupt"
Justin Zaun commented on JENKINS-11547 Jobs trigger continually even though there are no changes due to git repository being "corrupt" Is it at least possible to not trigger the build on this error and just wait till the next check? 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 -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-11547) Jobs trigger continually even though there are no changes due to git repository being "corrupt"
Justin Zaun commented on JENKINS-11547 Jobs trigger continually even though there are no changes due to git repository being "corrupt" Hi everyone. I registered this issue in the "kickstarting" section on FreedomSponsors. This means that if you need this issue that bad, you can go to http://www.freedomsponsors.org/core/issue/113/jobs-trigger-continually-even-though-there-are-no-changes-due-to-git-repository-being-corrupt and offer a few bucks for it. 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
