{"id":20823,"date":"2015-06-09T16:14:34","date_gmt":"2015-06-09T10:44:34","guid":{"rendered":"https:\/\/tothenewco.pro\/blog\/?p=20823"},"modified":"2016-11-30T11:20:36","modified_gmt":"2016-11-30T05:50:36","slug":"jenkins-implementing-project-based-matrix-authorization-strategy","status":"publish","type":"post","link":"https:\/\/tothenewco.pro\/blog\/jenkins-implementing-project-based-matrix-authorization-strategy\/","title":{"rendered":"Jenkins – Implementing Project-based Matrix Authorization Strategy"},"content":{"rendered":"

In one of my recent projects, while working on Jenkins<\/a>, I was required to create and implement a Project-based Matrix Authorization Strategy.<\/p>\n

Installation of Jenkins is a simple task, but it took me a while to implement this strategy and later I found it quite easy enough and thought of writing a blog.<\/p>\n

Project-based Matrix Authorization Strategy is an authorization method using which we can define which user or group can do what actions on which job. This gives us a fine-grained control over user\/group permissions per project.<\/p>\n

We are starting with a fresh Jenkins installation. Jenkins could be installed using the following commands:<\/p>\n

[js]wget -q -O – https:\/\/jenkins-ci.org\/debian\/jenkins-ci.org.key | sudo apt-key add –
\nsudo sh -c ‘echo deb http:\/\/pkg.jenkins-ci.org\/debian binary\/ > \/etc\/apt\/sources.list.d\/jenkins.list’
\nsudo apt-get update
\nsudo apt-get install jenkins
\n[\/js]<\/p>\n

Jenkins uses 8080 port by default so it could be accessible browsing below link
\nhttp:\/\/:8080<\/p>\n

We would be welcomed by this page:
\n\"jen1\"<\/a><\/p>\n

Now , click on \u201cManage Jenkins\u201d, we would be navigated to the following page:
\n\"jen2\"<\/a><\/p>\n

Click on \u201cConfigure Global Security\u201d to move to Global Security page:
\n\"jen3\"<\/a><\/p>\n

Check Enable security and more options would appear as shown below:
\n\"jen4\"<\/a><\/p>\n

As we are creating new users in Jenkins, we would be using \u201cJenkins\u2019 own user database\u201d. Select this radio button under \u201cSecurity Realm\u201d.<\/p>\n

Under Authorization, select \u201cProject-based Matrix Authorization Strategy\u201d and add two users, one administrator (say admin) and a regular user (say user1).<\/p>\n

All the checkboxes present besides users are for setting global permissions. Select all checkboxes against admin user to give admin full permissions.<\/p>\n

For user1, we are selecting read permissions under jobs. With this, user1 would now have read permission to view all jobs which we would be creating later on.<\/p>\n

We have to provide read permission under \u201cOverall\u201d category to any regular user otherwise the user won\u2019t be able to see anything after login.
\n\"jen5\"<\/a><\/p>\n

Save this setting and we would be navigated to login page.<\/p>\n

Sign up with user \u201cadmin\u201d and set a\u00a0password and other details and log in using admin user.
\n\"j15\"<\/a><\/p>\n

We can create \u201cuser1\u201d the same way after logging out of admin.<\/p>\n

Now, login in as admin user and create a job (say job1) and in configuration, select checkbox \u201cEnable Project-based security\u201d as shown below.
\n\"jen6\"<\/a><\/p>\n

Add user \u201cuser1\u201d, and give it \u201cbuild\u201d permissions under \u201cJob\u201d category and save the settings. This would enable \u201cuser1\u201d to build this job when user1 would log in.<\/p>\n

Alternatively, if we want user1 to have build permissions for every job which admin would create later on, we can select the\u00a0\u201cbuild\u201d checkbox under \u201cJob\u201d category in \u201cConfigure Global Security.\u201d<\/p>\n

Since, we have provided all permission to \u201cadmin\u201d while configuring global security, we do not need to add per project permission for admin.<\/p>\n

With this, we can set global as well as per-project permissions for every user.<\/p>\n","protected":false},"excerpt":{"rendered":"

In one of my recent projects, while working on Jenkins, I was required to create and implement a Project-based Matrix Authorization Strategy. Installation of Jenkins is a simple task, but it took me a while to implement this strategy and later I found it quite easy enough and thought of writing a blog. Project-based Matrix […]<\/p>\n","protected":false},"author":154,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"iawp_total_views":430,"footnotes":""},"categories":[1174,2348],"tags":[1853,248,2366,1892,227,1685,1682,2700,2701],"class_list":["post-20823","post","type-post","status-publish","format-standard","hentry","category-aws-2","category-devops-technology","tag-automation","tag-aws","tag-aws-devops","tag-devops","tag-grail-security","tag-install-jenkins","tag-jenkins","tag-project-based-security","tag-security-in-jenkins"],"aioseo_notices":[],"aioseo_head":"\n\t\t\n\t\n\t\n\t\n\t\n\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t