-
Bug
-
Resolution: Fixed
-
Major
-
None
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: <masked for security>
Client Secret: <masked for security>
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@ffffa64e: RemoteIpAddress: <masked for privacy>; 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
[JENKINS-21882] v1.551 + GitHub OAuth == broken api token access
Michael Crusoe
created issue -
Michael Crusoe
added a comment - Should I remove 'github-oauth' from the component list then? 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.
Michael Glass
added a comment - - edited 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. 
Jens Nielsen
added a comment - I'm seeing the same issue on the latest LTS release (1.532.2) downgrading to 1.532.1 fixes it.
Jens Nielsen
added a comment - I'm seeing the same issue on the latest LTS release (1.532.2) downgrading to 1.532.1 fixes it. Michael Glass
added a comment - confirmed still an issue with 1.552 
Soren Hansen
added a comment - ..and 1.553. Is anyone looking into this? Soren Hansen
added a comment - 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.
Soren Hansen
added a comment - 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. Soren Hansen
added a comment - 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.
Soren Hansen
added a comment - 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.
The contents of /systemInfo: