Jenkins configuration: Adding Users and Administrative permissions

Jenkins configuration: Adding Users and Administrative permissions

Reference article: http://www.cnblogs.com/zz0412/p/jenkins_jj_14.html

Let's talk about it today. Use the configuration of the Jenkins proprietary user database, and some common permissions configurations.

Configure user Registration

In the newly installed Jenkins, the default is not to set user rights, that is, access to the home page is administrator rights. For security, we need to configure user permissions.

1. Configure Jenkins permissions to add an administrator account

Click Manage jenkins->configure Global Security on the left to enter the following interface:

(1) Select "Enable Security";

A. Select "Jenkins ' own user database" in Security realm and tick "Allow users to sign up"

B. In authorization, select "matrix-based Security", in the User/group to add text box, enter admin, click "Add" button, you can see the user admin is added to the User/group table ；

C. In the User/group table, select all permissions for admin.

The above actions are as follows:

Settings such as, click Apply, click the Save button, the page will jump to the user login page. The Login/registration option will also appear in the upper right corner of the page.
Some students come here will have the question "that user and password is not yet set?" ", of course, no user name and password are set.
Perform the following actions:
In the upper right corner, click Sign up to enter
Enter the user name admin, password 111111, confirm password, full name, e-mail address, click the Sign Up button, the page will prompt Success, the default has been logged in with the Admin user, and admin is administrator, because before the admin selected all permissions.

2. Add other users (non-admin users)

(1) Users need to register an account on the Jenkins page. Method: Click on the upper right corner sign up and fill in the relevant information to complete the user registration. (Of course, you can sign in after registration, but no other permissions)

(2) The Admin user adds permissions for the user. Method:

A. Click Manage jenkins->configure Global Security on the left

B. In the User/group to add text box, enter cheers (the user name you just registered), click the "Add" button and the user is added to the User/group table.

C. In the To User/group table, locate the corresponding user cheers and select the appropriate permissions, then apply, save.

By now, the user added successfully, with the new user login to Jenkins, you can see that there are already relevant operational permissions.

The various permissions are as follows (you can view Help by placing your mouse over this permission on the configuration page):

overall ( global

credentials ( voucher )

slave ( node

job ( Task )

view ( view )

administer

read

runscripts

Uploadplugins

configureupdatecenter

create

update

view

delete

managedomains

Configure

delete

create

disconnect

connect

build

create

delete

configure

read

discover

build

workspace

cancel

create

delete

configure

read

Administrator (max)

Read

Run the script

Upgrade Plugin

Configure Upgrade Center

Create

Update

View

Delete

Admin domain

Configuration

Delete

Create

Disconnect Connection

Connection

Build

Create

Delete

Configuration

Read

redirect

Build

viewing workspaces

Cancel Build

Create

Delete

Configuration

Read

Some of these are more specific permissions:

The maximum permission is overall administer, which can do anything.

The most basic permission is overall read, the user must give the reading permission, otherwise can not see anything.

The job's discover permission is a wonderful privilege to help say that discover is lower than the read level. If an anonymous user (who does not have access to the job) accesses a job directly, the URL is redirected to the landing page. (After testing, this permission should be deprecated.) )

Credentials Managedomains This permission does not understand what to do, have to understand everyone together to exchange ha!

PS: If a user is given the read of overall and is not given the Read permission of the job, then the user cannot access the job. Cause: No permissions.

Others are some basic permissions, people choose according to their own needs.

Tips:

(1) When registering a user or admin, there will be a hint that the user is already present and the user needs to be deleted from the "/var/lib/jenkins/users" directory (for example, Linux).

(2) If the old Jenkins system forgets the password of admin, refer to the previous article:

Jenkins forgot Admin user account password

(3) After each user has 1-2 icons, the first is the reverse selection function (delete the currently selected permissions, select all other permissions), the second is the deletion function (delete the user)

Configure project security in the job, such as:

Original: 48711583

Jenkins configuration: Adding Users and Administrative permissions