Authentication of users is delegated to Github using the OAuth protocol. Authorization is based on the characteristics of the users Github user data that is retrieved through the Github API (effectively as the authenticated user).
The initial use case supported is that Jenkins is running jobs associated to a single or group of Github organizations. So we will authenticate users against the Github user data base and then authorize those users that are participants in one of the defined organizations with build and read permissions.
We also define a list of usernames that will have full admin rights on Jenkins.
There is also a flag to allow any authenticated user to have read access.
Since version 0.4 there is a way to authorize the use of the github-webhook callback url to receive post commit hooks from Github. This plugin has a checkbox that can allow Github to POST's to be received but you still need to run the Github Plugin to have the message trigger the build.
Further instructions are included in the plugin help.
You have to be a public member of the organization for the authorization to work correctly.
Skip to end of metadata Go to start of metadata