Authorization strategies (Matrix, role-based) in Jenkins - Commands & Configuration

Introduction

Jenkins controls who can do what using authorization strategies. These strategies help keep your projects safe by deciding who can build, configure, or manage jobs.

When you want to let some team members only run builds but not change settings

When you need to give admins full control but restrict others to view-only access

When you want to assign specific permissions to users or groups based on their roles

When you want to manage permissions easily for many users in a growing team

When you want to prevent accidental changes by limiting who can configure jobs

Commands

This command applies a Matrix-based authorization strategy using a Groovy script through Jenkins CLI. It sets specific permissions for users.

Terminal

java -jar jenkins-cli.jar -s http://localhost:8080/ groovy = < configure-matrix-auth.groovy

Expected Output

No output (command runs silently)

→

-s - Specifies the Jenkins server URL

This command applies a Role-Based authorization strategy using a Groovy script through Jenkins CLI. It defines roles and assigns users to them.

Terminal

java -jar jenkins-cli.jar -s http://localhost:8080/ groovy = < configure-role-based-auth.groovy

Expected Output

No output (command runs silently)

→

-s - Specifies the Jenkins server URL

This command checks the current user identity in Jenkins CLI to confirm permissions are applied correctly.

Terminal

java -jar jenkins-cli.jar -s http://localhost:8080/ who-am-i

Expected Output

Authenticated as: admin

Authorities: [authenticated, admin]

→

-s - Specifies the Jenkins server URL

Key Concept

If you remember nothing else from this pattern, remember: authorization strategies control who can do what in Jenkins to keep your projects safe and organized.

Common Mistakes

Not assigning any permissions to users after enabling Matrix or Role-Based strategy

This locks out users including admins, preventing any actions in Jenkins

Always assign at least one admin user full permissions before applying the strategy

Mixing Matrix and Role-Based strategies at the same time

Jenkins only allows one authorization strategy active, so this causes conflicts

Choose one strategy that fits your needs and configure only that one

Summary

Use Matrix strategy to assign specific permissions directly to users or groups.

Use Role-Based strategy to create roles with permissions and assign users to these roles.

Apply changes via Jenkins CLI with Groovy scripts to automate authorization setup.