[JIRA] [core] (JENKINS-21882) v1.551 + GitHub OAuth == broken api token access
Michael Glass commented on JENKINS-21882 v1.551 + GitHub OAuth == broken api token access wfm! Thanks so much, Soren 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 [email protected]. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-21882) v1.551 + GitHub OAuth == broken api token access
Tomas Bezdek commented on JENKINS-21882 v1.551 + GitHub OAuth == broken api token access works for me now! 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 [email protected]. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-21882) v1.551 + GitHub OAuth == broken api token access
Soren Hansen commented on JENKINS-21882 v1.551 + GitHub OAuth == broken api token access Plugin for testing can be found here: https://github.com/sorenh/github-oauth-plugin/releases/tag/0.16-pre-soren 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 [email protected]. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-21882) v1.551 + GitHub OAuth == broken api token access
Soren Hansen commented on JENKINS-21882 v1.551 + GitHub OAuth == broken api token access https://github.com/jenkinsci/github-oauth-plugin/pull/23 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 [email protected]. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-21882) v1.551 + GitHub OAuth == broken api token access
Soren Hansen commented on JENKINS-21882 v1.551 + GitHub OAuth == broken api token access Oh, found the problem! Jenkins's User class now calls the loadUserByUsername on the UserDetailsService from the SecurityComponents object on the SecurityRealm, but that doesn't actually call the loadUserByUsername method, but rather provides its own "fake" one in the Github OAuth plugin. 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 [email protected]. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-21882) v1.551 + GitHub OAuth == broken api token access
Jens Nielsen commented on JENKINS-21882 v1.551 + GitHub OAuth == broken api token access That seems likely and explains why it works on the latest LTS but not on the regular version. 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 [email protected]. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-21882) v1.551 + GitHub OAuth == broken api token access
Soren Hansen commented on JENKINS-21882 v1.551 + GitHub OAuth == broken api token access It seems this broke again after I fixed it. AFter upgrading my Jenkins instance, it again does not work for me. A number of bugs seem related: JENKINS-22346 JENKINS-20064 JENKINS-9258 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 [email protected]. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-21882) v1.551 + GitHub OAuth == broken api token access
Michael Glass commented on JENKINS-21882 v1.551 + GitHub OAuth == broken api token access Peter Downs 0.15-snapshot solves some peoples' issues but not everyones' 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 [email protected]. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-21882) v1.551 + GitHub OAuth == broken api token access
Peter Downs commented on JENKINS-21882 v1.551 + GitHub OAuth == broken api token access Is there any further progress on this? It's unclear from this thread if the issue is resolved by using the 0.15-SNAPSHOT .hpi. 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 [email protected]. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-21882) v1.551 + GitHub OAuth == broken api token access
no no commented on JENKINS-21882 v1.551 + GitHub OAuth == broken api token access Jenkins 1.557, 558 +1 Michael Glass 30/Mar/14 7:49 PM: 401 Unexpected authentication type ... UsernamePasswordAuthenticationToken with curl +1 Jens Nielsen 25/Mar/14 11:01 AM: jenkins plugin manager has latest Github Oauth Plugin v0.14 Soren, is swapping the installed github-oauth.jpi for github-oauth.hpi from your link sufficient to upgrade the plugin to 0.15-SNAPSHOT? If so, I can confirm the 401 error produces no output in /var/log/jenkins/jenkins.log. 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 [email protected]. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-21882) v1.551 + GitHub OAuth == broken api token access
Tomas Bezdek commented on JENKINS-21882 v1.551 + GitHub OAuth == broken api token access yes, the update center has "0.15-SNAPSHOT (private-04/02/2014 23:27-soren)" as version for oauth plugin. the problem must be in the plugin, because when access control is set to jenkins own db, it works 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 [email protected]. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-21882) v1.551 + GitHub OAuth == broken api token access
Soren Hansen commented on JENKINS-21882 v1.551 + GitHub OAuth == broken api token access After installing the linked plugin and restarting Jenkins? If so, I think this is over my head. It would appear the github oauth plugin isn't even being invoked, and I have no idea why that might be the case. 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 [email protected]. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-21882) v1.551 + GitHub OAuth == broken api token access
Tomas Bezdek commented on JENKINS-21882 v1.551 + GitHub OAuth == broken api token access I have jenkins-job-builder as one of the jobs in jenkins, which authenticates using api token. I've run the job twice, once with enabled jenkins security and once with disabled, but all I can see in log is this: Apr 2, 2014 9:53:20 PM hudson.model.Run execute INFO: jenkis-job-builder #121 main build action completed: FAILURE Apr 2, 2014 9:54:09 PM hudson.model.Run execute INFO: jenkis-job-builder #122 main build action completed: SUCCESS no log entries from the oauth plugin... 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 [email protected]. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-21882) v1.551 + GitHub OAuth == broken api token access
Soren Hansen commented on JENKINS-21882 v1.551 + GitHub OAuth == broken api token access If you could grab the hpi from this url, install it, and do something like "tail -f /var/log/jenkins/jenkins.log | grep XXX" and try, I hope that should help me in the right direction. https://github.com/sorenh/github-oauth-plugin/releases/tag/0.15-moredebugging.1 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 [email protected]. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-21882) v1.551 + GitHub OAuth == broken api token access
Tomas Bezdek commented on JENKINS-21882 v1.551 + GitHub OAuth == broken api token access the server-side log doesn't show any exceptions or related messages (with INFO level on) 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 [email protected]. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-21882) v1.551 + GitHub OAuth == broken api token access
Soren Hansen commented on JENKINS-21882 v1.551 + GitHub OAuth == broken api token access I was really hoping for relevant parts of the server side log file (for me it's located in /var/log/jenkins/jenkins.log). Any chance you can dig that up for me? 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 [email protected]. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-21882) v1.551 + GitHub OAuth == broken api token access
Michael Glass edited a comment on JENKINS-21882 v1.551 + GitHub OAuth == broken api token access Sorry needed a weekend (p.s. Soren, thanks so much for your help in the first place) I just upgraded to 1.556 and your binary of the github oauth plugin. When I $ curl --user [masked username]:[masked api key] --data "" [jenkins api endpoint] I get (with a lot of html formatting removed) Error 401 Unexpected authentication type: org.acegisecurity.providers.UsernamePasswordAuthenticationToken@94008f0a: Username:[masked username]; Password: [PROTECTED]; Authenticated: false; Details: org.acegisecurity.ui.WebAuthenticationDetails@957e: RemoteIpAddress: 127.0.0.1; SessionId: null; Not granted any authorities How can I get more detailed log info? The jenkins logging page is a little tough for me to parse given the fact that they don't give me target systems to log. (hudson.? org.jenkinsci.plugins?) 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 [email protected]. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-21882) v1.551 + GitHub OAuth == broken api token access
Michael Glass edited a comment on JENKINS-21882 v1.551 + GitHub OAuth == broken api token access Sorry needed a weekend (p.s. Soren, thanks so much for your help in the first place) I just upgraded to 1.556 and your binary of the github oauth plugin. When I $ curl --user [masked username]:[masked api key] --data "" [jenkins api endpoint] I get (with a lot of html formatting removed) Error 401 Unexpected authentication type: org.acegisecurity.providers.UsernamePasswordAuthenticationToken@94008f0a: Username:[masked username]; Password: [PROTECTED]; Authenticated: false; Details: org.acegisecurity.ui.WebAuthenticationDetails@957e: RemoteIpAddress: 127.0.0.1; SessionId: null; Not granted any authorities How can I get more detailed log info? The jenkins logging page is a little touch for me to parse given the fact that they don't give me target systems to log. (hudson.? org.jenkinsci.plugins?) 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 [email protected]. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-21882) v1.551 + GitHub OAuth == broken api token access
Michael Glass commented on JENKINS-21882 v1.551 + GitHub OAuth == broken api token access Sorry needed a weekend (p.s. Soren, thanks so much for your help in the first place) I just upgraded to 1.556 and your binary of the github oauth plugin. When I $ curl --user [masked username]:[masked api key] --data "" [jenkins api endpoint] I get (with a lot of html formatting removed) Error 401 Unexpected authentication type: org.acegisecurity.providers.UsernamePasswordAuthenticationToken@94008f0a: Username:[masked username]; Password: [PROTECTED]; Authenticated: false; Details: org.acegisecurity.ui.WebAuthenticationDetails@957e: RemoteIpAddress: 127.0.0.1; SessionId: null; Not granted any authorities 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 [email protected]. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-21882) v1.551 + GitHub OAuth == broken api token access
Soren Hansen commented on JENKINS-21882 v1.551 + GitHub OAuth == broken api token access Can you share what is recorded in the log file when you try this? I'd like to understand why my patch might not work for you, since it works for me. 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 [email protected]. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-21882) v1.551 + GitHub OAuth == broken api token access
Jens Nielsen commented on JENKINS-21882 v1.551 + GitHub OAuth == broken api token access Another thing. The latest release (0.15) does not appear in the update center nor on the download server here https://updates.jenkins-ci.org/download/plugins/ 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 [email protected]. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-21882) v1.551 + GitHub OAuth == broken api token access
Jens Nielsen commented on JENKINS-21882 v1.551 + GitHub OAuth == broken api token access The issue was resolved for me on the 1.532.2 lts (same time as 1.551) release. I have not tested any of the regular releases. Is it possible that another issue broke the this on one of the release following this i.e. 1.552 .. 1.556 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 [email protected]. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-21882) v1.551 + GitHub OAuth == broken api token access
Michael Glass reopened JENKINS-21882 v1.551 + GitHub OAuth == broken api token access tried 0.15 and received the same error. Change By: Michael Glass (25/Mar/14 5:26 AM) Resolution: Fixed Status: Resolved Reopened 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 [email protected]. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-21882) v1.551 + GitHub OAuth == broken api token access
Michael Glass commented on JENKINS-21882 v1.551 + GitHub OAuth == broken api token access Sam: I tried Soren's fix to no avail. Same error. Thoughts? 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 [email protected]. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-21882) v1.551 + GitHub OAuth == broken api token access
Sam Kottler resolved JENKINS-21882 as Fixed v1.551 + GitHub OAuth == broken api token access This has been fixed in 0.15. Please report any additional issues you may find in the release. Thanks for your patience on this one! Change By: Sam Kottler (24/Mar/14 4:50 AM) Status: Open Resolved Fix Version/s: current Resolution: Fixed 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 [email protected]. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-21882) v1.551 + GitHub OAuth == broken api token access
Soren Hansen commented on JENKINS-21882 v1.551 + GitHub OAuth == broken api token access Filed a pull request: https://github.com/jenkinsci/github-oauth-plugin/pull/18 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 [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-21882) v1.551 + GitHub OAuth == broken api token access
Soren Hansen commented on JENKINS-21882 v1.551 + GitHub OAuth == broken api token access Or perhaps this is correct.. The authToken is specific to a user, so in this context it couldn't be set... and I don't suppose GitHub reveals information about users without authentication. 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 [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-21882) v1.551 + GitHub OAuth == broken api token access
Soren Hansen commented on JENKINS-21882 v1.551 + GitHub OAuth == broken api token access This seems to have been introduced by https://github.com/jenkinsci/jenkins/commit/5548b5220cfd496831b5721124189ff18fbb12a3 This makes it work again: https://github.com/sorenh/github-oauth-plugin/commit/da5c787cf72580f06c6a6318bf1b8a73071e8bcd But I'm fairly sure it's not the right fix: The correct fix should be to make sure the authtoken is set. I don't know why it isn't. The correct exception to throw in that situation seems like DataAccessException, but that would not actually make this work again. Perhaps someone else can shed some light on why authtoken might be null at this point? I've never looked at Jenkins internals before (and haven't really touched java in around a decade), so any further input would be greatly appreciated. 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 [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-21882) v1.551 + GitHub OAuth == broken api token access
Soren Hansen commented on JENKINS-21882 v1.551 + GitHub OAuth == broken api token access ..and 1.553. Is anyone looking into this? 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 [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-21882) v1.551 + GitHub OAuth == broken api token access
Michael Glass commented on JENKINS-21882 v1.551 + GitHub OAuth == broken api token access confirmed still an issue with 1.552 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 [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-21882) v1.551 + GitHub OAuth == broken api token access
Jens Nielsen commented on JENKINS-21882 v1.551 + GitHub OAuth == broken api token access I'm seeing the same issue on the latest LTS release (1.532.2) downgrading to 1.532.1 fixes 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 -- 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 [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-21882) v1.551 + GitHub OAuth == broken api token access
Michael Glass edited a comment on JENKINS-21882 v1.551 + GitHub OAuth == broken api token access if you want username/api token access to jenkins, either disable the github oauth plugin or roll back to version jenkins 1.550 or before. 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 [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-21882) v1.551 + GitHub OAuth == broken api token access
Michael Glass commented on JENKINS-21882 v1.551 + GitHub OAuth == broken api token access if you want API access to jenkins, either disable the github oauth plugin or roll back to version jenkins 1.550 or before. 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 [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-21882) v1.551 + GitHub OAuth == broken api token access
Michael Crusoe commented on JENKINS-21882 v1.551 + GitHub OAuth == broken api token access Should I remove 'github-oauth' from the component list then? 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 [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-21882) v1.551 + GitHub OAuth == broken api token access
Michael Glass edited a comment on JENKINS-21882 v1.551 + GitHub OAuth == broken api token access confirmed: rolling back to git 1.550 fixes auth issues 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 [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-21882) v1.551 + GitHub OAuth == broken api token access
Michael Glass commented on JENKINS-21882 v1.551 + GitHub OAuth == broken api token access I noticed the same issue. When I rolled back my jenkins version, however, I still had auth issues. Can you confirm that this is a regression caused by 1.551? 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 [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-21882) v1.551 + GitHub OAuth == broken api token access
Michael Crusoe commented on JENKINS-21882 v1.551 + GitHub OAuth == broken api token access The contents of /systemInfo: System Properties Name ↓ Value executable-war /usr/share/jenkins/jenkins.war file.encoding UTF-8 file.encoding.pkg sun.io file.separator / hudson.diyChunking true java.awt.graphicsenv sun.awt.X11GraphicsEnvironment java.awt.headless true java.awt.printerjob sun.print.PSPrinterJob java.class.path /usr/share/jenkins/jenkins.war java.class.version 50.0 java.endorsed.dirs /usr/lib/jvm/java-6-openjdk-amd64/jre/lib/endorsed java.ext.dirs /usr/lib/jvm/java-6-openjdk-amd64/jre/lib/ext:/usr/java/packages/lib/ext java.home /usr/lib/jvm/java-6-openjdk-amd64/jre java.io.tmpdir /tmp java.library.path /usr/lib/jvm/java-6-openjdk-amd64/jre/lib/amd64/server:/usr/lib/jvm/java-6-openjdk-amd64/jre/lib/amd64:/usr/lib/jvm/java-6-openjdk-amd64/jre/../lib/amd64:/usr/java/packages/lib/amd64:/usr/lib/x86_64-linux-gnu/jni:/lib/x86_64-linux-gnu:/usr/lib/x86_64-linux-gnu:/usr/lib/jni:/lib:/usr/lib java.runtime.name OpenJDK Runtime Environment java.runtime.version 1.6.0_27-b27 java.specification.name Java Platform API Specification java.specification.vendor Sun Microsystems Inc. java.specification.version 1.6 java.vendor Sun Microsystems Inc. java.vendor.url http://java.sun.com/ java.vendor.url.bug http://java.sun.com/cgi-bin/bugreport.cgi java.version 1.6.0_27 java.vm.info mixed mode java.vm.name OpenJDK 64-Bit Server VM java.vm.specification.name Java Virtual Machine Specification java.vm.specification.vendor Sun Microsystems Inc. java.vm.specification.version 1.0 java.vm.vendor Sun Microsystems Inc. java.vm.version 20.0-b12 jna.platform.library.path /usr/lib/x86_64-linux-gnu:/lib/x86_64-linux-gnu:/lib64:/usr/lib:/lib line.separator mail.smtp.sendpartial true mail.smtps.sendpartial true os.arch amd64 os.name Linux os.version 3.2.0-58-virtual path.separator : sun.arch.data.model 64 sun.boot.class.path /usr/lib/jvm/java-6-openjdk-amd64/jre/lib/resources.jar:/usr/lib/jvm/java-6-openjdk-amd64/jre/lib/rt.jar:/usr/lib/jvm/java-6-openjdk-amd64/jre/lib/sunrsasign.jar:/usr/lib/jvm/java-6-openjdk-amd64/jre/lib/jsse.jar:/usr/lib/jvm/java-6-openjdk-amd64/jre/lib/jce.jar:/usr/lib/jvm/java-6-openjdk-amd64/jre/lib/charsets.jar:/usr/lib/jvm/java-6-openjdk-amd64/jre/lib/netx.jar:/usr/lib/jvm/java-6-openjdk-amd64/jre/lib/plugin.jar:/usr/lib/jvm/java-6-openjdk-amd64/jre/lib/rhino.jar:/usr/lib/jvm/java-6-openjdk-amd64/jre/lib/modules/jdk.boot.jar:/usr/lib/jvm/java-6-openjdk-amd64/jre/classes sun.boot.library.path /usr/lib/jvm/java-6-openjdk-amd64/jre/lib/amd64 sun.cpu.endian little sun.cpu.isalist sun.io.unicode.encoding UnicodeLittle sun.java.command /usr/share/jenkins/jenkins.war --webroot=/var/cache/jenkins/war --httpPort=8080 --ajp13Port=-1 sun.java.launcher SUN_STANDARD sun.jnu.encoding UTF-8 sun.management.compiler HotSpot 64-Bit Tiered Compilers sun.os.patch.level unknown svnkit.http.methods Digest,Basic,NTLM,Negotiate svnkit.ssh2.persistent false user.country US user.dir / user.home /var/lib/jenkins user.language en user.name jenkins user.timezone America/New_York Environment Variables Name ↓ Value _ /usr/bin/daemon HOME /var/lib/jenkins JENKINS_HOME /var/lib/jenkins LANG en_US.UTF-8 LD_LIBRARY_PATH /usr/lib/jvm/java-6-openjdk-amd64/jre/lib/amd64/server:/usr/lib/jvm/java-6-openjdk-amd64/jre/lib/amd64:/usr/lib/jvm/java-6-openjdk-amd64/jre/../lib/amd64 LOGNAME jenkins MAIL /var/mail/jenkins PATH /usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games PWD /var/lib/jenkins SHELL /bin/bash SHLVL 1 TERM screen USER jenkins Plugins Name ↓ Version Enabled Pinned ant 1.2 true false credentials 1.10 true true cvs 2.11 true false external-monitor-job 1.2 true false github-api 1.44 true false github-oauth 0.14 true false javadoc 1.1 true false ldap 1.8 true true mailer 1.8 true true matrix-auth 1.1 true false maven-plugin 2.1 true false pam-auth 1.1 true false scm-api 0.2 true false ssh-credentials 1.6.1 true true ssh-slaves 1.6 true true subversion 2.2 true true translation 1.11 true true windows-slaves 1.0 true false 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] [core] (JENKINS-21882) v1.551 + GitHub OAuth == broken api token access
Michael Crusoe
created JENKINS-21882
v1.551 + GitHub OAuth == broken api token access
Issue Type:
Bug
Affects Versions:
current
Assignee:
Sam Kottler
Components:
core, github-oauth
Created:
19/Feb/14 5:10 PM
Description:
I've reproduced this by setting up a fresh Jenkins install.
Here are my notes from that install:
On Ubuntu 12.04.4 LTS
sudo sh -c 'echo deb http://pkg.jenkins-ci.org/debian binary/ > /etc/apt/sources.list.d/jenkins.list'
wget -q -O - http://pkg.jenkins-ci.org/debian/jenkins-ci.org.key | sudo apt-key add -
sudo apt-get update
sudo apt-get install jenkins
Visit http://host:8080/configureSecurity/
Check "Enable security"
Under the "Access Control" section choose the option "Jenkins’ own user database" under the "Security Realm" header.
Choose "Save" at the bottom of the page.
Visit http://host:8080/signup
Fill out form matching the username to your github username.
Return to Visit http://host:8080/configureSecurity/
Under the "Access Control" section unselect "Allow users to sign up" under "Jenkins’ own user database" which is under the "Security Realm" header.
Under the "Authorization" heading select the option "Logged-in users can do anything".
Choose "Save" at the bottom of the page.
Visit http://host:8080/pluginManager/
Select all plugins with available updates using the link at the bottom of the page and then "install without restart".
On the subsequent screen choose "Restart Jenkins when installation is complete and no jobs are running."
At this point running the following produces no error:
curl --url http://host:8080/user/mr-c --user mr-c:${api_token}
Install the Github OAuth Plugin (grabs the GitHub API Plugin)
Return to Visit http://host:8080/configureSecurity/
Under the "Access Control" section choose the option "Github Authentication Plugin" under the "Security Realm" header.
GitHub Web URI: https://github.com
GitHub API URI: https://api.github.com
Client ID:
Client Secret:
Under the "Authorization" heading select the option "Github Commiter Authorization Strategy".
Admin User Names: mr-c
Participant in Organization: ged-lab
Grant READ permissions to all Authenticated Users: yes
Grant READ permissions for /github-webhook: yes
Grant READ permissions for Anonymous Users: yes
Choose "Save" at the bottom of the page.
Now the command:
curl --url http://host:8080/user/mr-c --user mr-c:${api_token}
produces this output:
HTTP ERROR 401
Problem accessing /user/mr-c. Reason:
Unexpected authentication type: org.acegisecurity.providers.UsernamePasswordAuthenticationToken@23fcf1a8: Username: mr-c; Password: [PROTECTED]; Authenticated: false; Details: org.acegisecurity.ui.WebAuthenticationDetails@a64e: RemoteIpAddress: ; SessionId: null; Not granted any authorities
This became a problem for me while trying to update my OS X slave using rhwood's jenkins-slave-osx script. I've filed a ticket there:
https://github.com/rhwood/jenkins-slave-osx/issues/33
Project:
Jenkins
Priority:
Major
Reporter:
Michael Crusoe
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 [email protected].
For more option
