Authentication methods (LDAP, SAML) in Jenkins - Step-by-Step Execution

Process Flow - Authentication methods (LDAP, SAML)

User tries to login

↓

Select Auth Method

↓

LDAP Auth

↓

Query LDAP

↓

Validate User

↓

Grant Access

↓

Access Jenkins

User login triggers either LDAP or SAML authentication flow, both validate credentials and grant access to Jenkins.

Execution Sample

Jenkins

User logs in -> Choose LDAP or SAML -> Authenticate -> Access Jenkins

Shows the step-by-step flow of user authentication using LDAP or SAML in Jenkins.

Process Table

Step	Action	Method	System Request	System Response	Result
1	User enters credentials	N/A	N/A	N/A	Credentials captured
2	Select authentication method	LDAP	Send LDAP query	LDAP server responds	User info retrieved
3	Validate credentials	LDAP	Check password	Password match	Authentication success
4	Grant access	LDAP	N/A	N/A	User logged in
5	User enters credentials	N/A	N/A	N/A	Credentials captured
6	Select authentication method	SAML	Redirect to SAML IdP	IdP login page	User redirected
7	User authenticates at IdP	SAML	Submit credentials	SAML token issued	Token received
8	Validate SAML token	SAML	Verify token signature	Token valid	Authentication success
9	Grant access	SAML	N/A	N/A	User logged in

💡 Authentication completes when user credentials are validated and access is granted.

Status Tracker

Variable	Start	After LDAP Step 2	After LDAP Step 3	After SAML Step 7	After SAML Step 8	Final
Credentials	None	Captured	Validated	Captured	Validated	Used for login
Auth Method	None	LDAP	LDAP	SAML	SAML	Set per login
User Info	None	Retrieved	Confirmed	None	Received via token	Confirmed
Access Status	No	No	Yes	No	Yes	Yes

Key Moments - 3 Insights

Why does LDAP require querying a server while SAML redirects the user?

LDAP directly queries the directory server to check credentials (see execution_table rows 2-3), while SAML uses a redirect to an external Identity Provider (rows 6-7) for authentication.

What happens if the SAML token is invalid?

If the SAML token fails validation (not shown in table but implied after row 8), access is denied and login fails, unlike LDAP which validates credentials directly.

Why are there two 'User enters credentials' steps?

Because in LDAP, credentials are entered directly in Jenkins (row 1), but in SAML, credentials are entered at the external IdP after redirect (row 7).

Visual Quiz - 3 Questions

Look at the execution table, at which step does LDAP validate the user's password?

A Step 2

B Step 3

C Step 6

D Step 8

💡 Hint

Check the 'Action' and 'Result' columns for LDAP steps in the execution_table.

According to the variable tracker, when does 'Access Status' become 'Yes' for SAML?

A After Step 6

B After Step 7

C After Step 8

D After Step 3

💡 Hint

Look at the 'Access Status' row and the columns for SAML steps in variable_tracker.

If the user chooses LDAP but the LDAP server does not respond, which step would fail?

A Step 2

B Step 3

C Step 6

D Step 7

💡 Hint

Refer to the 'System Request' and 'System Response' columns for LDAP in execution_table.

Concept Snapshot

Authentication methods in Jenkins:
- LDAP: Jenkins queries LDAP server directly to validate credentials.
- SAML: Jenkins redirects user to external Identity Provider (IdP) for login.
- Both methods validate user and grant access.
- LDAP handles credentials internally; SAML uses tokens from IdP.
- Choose method based on your organization's setup.

Full Transcript

This visual execution shows how Jenkins authenticates users using LDAP or SAML. When a user logs in, Jenkins captures credentials and selects the authentication method. For LDAP, Jenkins sends a query to the LDAP server to retrieve user info and validate the password. If successful, access is granted. For SAML, Jenkins redirects the user to an external Identity Provider where the user logs in. The IdP sends back a SAML token, which Jenkins validates before granting access. Variables like credentials, authentication method, user info, and access status change step-by-step during the process. Key points include the difference in where credentials are entered and how validation happens. The quizzes test understanding of these steps and variable changes.

Practice

1. What is the main purpose of using LDAP authentication in Jenkins?

easy

A. To connect Jenkins to an existing directory server for user login

B. To enable Jenkins to send emails automatically

C. To create new user accounts inside Jenkins manually

D. To backup Jenkins configuration files

Solution

1. Step 1: Understand LDAP role in Jenkins

   LDAP allows Jenkins to use an external directory server for user authentication instead of managing users internally.

2. Step 2: Identify the correct purpose

   Connecting Jenkins to an existing directory server helps reuse user accounts and centralize login management.

3. Final Answer:

   To connect Jenkins to an existing directory server for user login -> Option A

4. Quick Check:

   LDAP = External directory login [OK]

Hint: LDAP connects Jenkins to directory servers for login [OK]

Common Mistakes:

• Confusing LDAP with email or backup functions
• Thinking LDAP creates users inside Jenkins
• Mixing LDAP with SAML single sign-on

2. Which of the following is the correct Jenkins configuration snippet to enable LDAP authentication?

easy

A. securityRealm {
ldap {
server 'ldap://ldap.example.com'
}
}

B. securityRealm {
saml {
idp 'https://idp.example.com'
}
}

C. securityRealm {
local {
users ['admin']
}
}

D. securityRealm {
oauth {
provider 'github'
}
}

Solution

1. Step 1: Identify LDAP configuration syntax

   The snippet with ldap and server 'ldap://...' matches LDAP setup in Jenkins.

2. Step 2: Exclude other authentication methods

   Options with saml, local, or oauth are for different authentication types, not LDAP.

3. Final Answer:

   securityRealm { ldap { server 'ldap://ldap.example.com' } } -> Option A

4. Quick Check:

   LDAP config uses ldap { server } [OK]

Hint: LDAP config uses 'ldap { server "ldap://..." }' block [OK]

Common Mistakes:

• Confusing LDAP with SAML or OAuth syntax
• Using local user config for LDAP
• Missing the ldap server URL

3. Given this Jenkins SAML configuration snippet, what will happen when a user tries to log in?

securityRealm {
  saml {
    idp 'https://idp.example.com'
    usernameField 'email'
  }
}

medium

A. Users must enter their LDAP password to log in

B. Jenkins will authenticate users via the specified identity provider using their email as username

C. Jenkins will ignore the SAML config and use local users

D. Jenkins will fail to start due to syntax error

Solution

1. Step 1: Analyze SAML configuration

   The snippet sets Jenkins to use SAML authentication with an identity provider URL and specifies the username field as 'email'.

2. Step 2: Understand login behavior

   Users will be redirected to the identity provider for login, and their email will be used as the Jenkins username.

3. Final Answer:

   Jenkins will authenticate users via the specified identity provider using their email as username -> Option B

4. Quick Check:

   SAML uses IdP and usernameField [OK]

Hint: SAML uses IdP URL and usernameField for login [OK]

Common Mistakes:

• Assuming local or LDAP login instead of SAML
• Confusing usernameField with password
• Thinking this causes startup failure

4. You configured Jenkins with LDAP authentication but users cannot log in. Which of these is the most likely cause?

medium

A. The Jenkins server has no internet connection

B. The Jenkins home directory is missing

C. The Jenkins user database is empty

D. The LDAP server URL is incorrect or unreachable

Solution

1. Step 1: Identify common LDAP login issues

   If users cannot log in with LDAP, a frequent cause is that Jenkins cannot reach the LDAP server due to wrong URL or network issues.

2. Step 2: Exclude unrelated causes

   Internet connection is not always required if LDAP is internal; empty Jenkins user DB is irrelevant with LDAP; missing home directory causes other errors.

3. Final Answer:

   The LDAP server URL is incorrect or unreachable -> Option D

4. Quick Check:

   LDAP login fails if server URL wrong [OK]

Hint: Check LDAP server URL first if login fails [OK]

Common Mistakes:

• Blaming Jenkins user DB when LDAP is used
• Assuming internet is always needed
• Ignoring network connectivity to LDAP

5. You want Jenkins to allow users to log in using SAML with your company's identity provider and also fallback to LDAP if SAML fails. Which approach is best?

hard

A. Configure LDAP first and then SAML, Jenkins will try both automatically

B. Use only LDAP because Jenkins does not support multiple authentication methods

C. Configure SAML as primary and LDAP as secondary authentication in Jenkins security settings

D. Set up two separate Jenkins instances, one for SAML and one for LDAP

Solution

1. Step 1: Understand Jenkins authentication chaining

   Jenkins supports configuring multiple authentication methods with priority, allowing fallback from SAML to LDAP.

2. Step 2: Choose correct configuration order

   Setting SAML as primary and LDAP as secondary lets Jenkins try SAML first, then LDAP if SAML fails.

3. Step 3: Exclude incorrect options

   Only LDAP is limiting; Jenkins can chain methods; separate instances add complexity; LDAP first then SAML is not standard fallback order.

4. Final Answer:

   Configure SAML as primary and LDAP as secondary authentication in Jenkins security settings -> Option C

5. Quick Check:

   Primary SAML with LDAP fallback = Configure SAML as primary and LDAP as secondary authentication in Jenkins security settings [OK]

Hint: Set SAML primary, LDAP secondary for fallback [OK]

Common Mistakes:

• Thinking Jenkins cannot chain authentication methods
• Using separate Jenkins instances unnecessarily
• Configuring LDAP before SAML for fallback