Jenkins - user management, authorization policy configuration and Jenkins security configuration management

1. Jenkins user management

Jenkins is a multi-user system.
Jenkins can use other plug-ins to allow different users to access different functions of the system.
Users can register or administrators can add, delete, modify and check

1. Enter the system management interface

insert image description here

2. Create a user

insert image description here

3. Edit user information

insert image description here

insert image description here

4. Edit user information

insert image description here

5. Delete user information

insert image description here

2. Jenkins authorization policy configuration

1. Authorization policy plugin

Different users have different requirements for system functions
. For safety considerations, key and important system functions need to be restricted from the use of some users
. For convenience considerations, system functions need to be customized according to different users.

2. Install the plug-in: Role-based Authorization Strategy

insert image description here
insert image description here

3. Management roles

insert image description here
insert image description here

a. Global roles

insert image description here

b. Item roles

insert image description here

c. Node roles Node roles

insert image description here

4. Assign roles

insert image description here

insert image description here

3. Jenkins security configuration management

1. Enter the system management interface

insert image description here

2. Introduction to security configuration

Jenkins has good scalability, such as remote execution, interface calls, etc., but it needs to consider network security factors, so Jenkins configures these functions and sets them on demand.

3. Detailed security configuration options

Configuration items:

Authentication
Token Formatter Proxy
Cross
Site Request Forgery Protection (CSRF)
Hidden Security Warning
API Token
SSH Server

Authentication

Don't remember me: If checked, the check box to keep logged in will not appear on the login page
Security Domain

Jenkins proprietary user database
insert image description here
insert image description here
When the number of users is small, it is not recommended to enable this function, and the administrator can directly create users and assign permissions.
Servlet container proxy
None
authorization policy
insert image description here

Any user can do anything (no restrictions)
logged in users can do anything
Legacy Mode

markup formatter

Plain Text
insert image description here

acting

insert image description here
proxy TCP port

Designated port (50000): Port 50000 opened by jenkins to the outside world,
randomly selected
, disabled

Cross Site Request Forgery Protection

Crumb Issuer: Use the default debris generator by default to
enable proxy compatibility
insert image description here

API Token

insert image description here
Generate a legacy API token for each newly created user (not recommended)
Allow users to manually create a legacy API token (not recommended)
Enable API Token usage statistics (recommended)

SSH Server

insert image description here
Specified Port
Randomly Selected
Disabled

Guess you like

Origin blog.csdn.net/YZL40514131/article/details/130143433