Git Version Control Cookbook

There's more...

Authentication is only half of the equation. Identifying a user is, of course, important, but what we do with that information is critical as well. Here is where authorization comes into play, which, keeping the question analogy, aims to answer the question: Given that the person trying to access the service is X, what is he allowed and not allowed to do?

The way we configured the Jenkins instance, anybody able to log in will be able to do anything. This might not be the desired behavior, which leads to another section of the Global Security page in Jenkins.

You will find a section called Authorization, which provides many options. One is the GitHub Committer Authorization Strategy, which determines if a user is allowed to ...