Chapter 3: Managing Jenkins – Users, Credentials, and Permissions
This guide explains how to configure Jenkins user accounts, manage credentials for secure storage, and control access permissions using role‑based strategies, covering viewing, creating, updating, and deleting users and credentials as well as assigning global, project, and node roles.
Chapter 3: Managing Jenkins (Users, Credentials, Permissions)
1. User Management
Configure user access entry: System Management → Global Security Configuration.
By default, Jenkins uses its own database for storage.
Optionally integrate LDAP or GitLab services (requires installing the appropriate plugin).
1.1 View Users
Using Jenkins' proprietary database as an example, the user management entry: System Management → Manage Users.
1.2 Create User
1.3 Delete User
1.4 Update User
2. Credential Management
Credentials can store encrypted database passwords, GitLab password information, etc.
Credential types:
2.1 View Credentials
Credentials → System → Global Credentials
2.2 Create Credential
2.3 Delete Credential
2.4 Update Credential
2.5 Move Credential
Credentials support multiple domains and can be moved to other domains.
3. Permission Management
Permissions default to Role‑Based Strategy; other methods are shown in the diagram.
3.1 Manage Permissions
System Settings → Manage and Assign Roles → Manage Roles
Global roles: add users and groups, assign which group a user belongs to.
Project roles: add users or groups to a specific project or set of projects.
Slave roles: add users or groups to a specific node or set of nodes.
3.2 Global Permissions
Credential parameters, string parameters, password parameters, boolean parameters, file parameters, text parameters, runtime parameters, option parameters.
3.3 Project Permissions
3.4 Permission Assignment
System Settings → Manage and Assign Roles → Assign Roles
DevOps Cloud Academy
Exploring industry DevOps practices and technical expertise.
How this landed with the community
Was this worth your time?
0 Comments
Thoughtful readers leave field notes, pushback, and hard-won operational detail here.