Creating first admin user in Jenkins - Quick Revision & Summary

Recall & Review

beginner

What is the purpose of creating the first admin user in Jenkins?

The first admin user in Jenkins is created to securely manage Jenkins settings and control access to the system. This user has full permissions to configure Jenkins and manage other users.

intermediate

Which file do you edit to create the first admin user manually in Jenkins?

You edit the config.xml file inside the Jenkins home directory or use the Jenkins setup wizard to create the first admin user.

beginner

What command can you use to restart Jenkins after creating the first admin user?

You can restart Jenkins by running sudo systemctl restart jenkins on Linux systems where Jenkins is installed as a service.

beginner

What is the default URL to access Jenkins after installation?

The default URL is http://localhost:8080 where you can complete the setup and create the first admin user.

beginner

Why is it important to save the initial admin password during Jenkins setup?

The initial admin password is required to unlock Jenkins for the first time and create the first admin user. Without it, you cannot proceed with Jenkins setup.

Where do you find the initial admin password for Jenkins after installation?

A It is emailed automatically

B In the Jenkins dashboard

C In the Jenkins logs only

D In the <code>/var/lib/jenkins/secrets/initialAdminPassword</code> file

The initial admin password is stored in the initialAdminPassword file inside the Jenkins secrets directory.

What is the first step after installing Jenkins to create an admin user?

A Create a new job

B Restart Jenkins service

C Unlock Jenkins using the initial admin password

D Install plugins

You must first unlock Jenkins with the initial admin password to proceed with creating the first admin user.

Which Jenkins feature helps you create the first admin user during setup?

A Script console

B Setup wizard

C Job configuration

D Build triggers

The setup wizard guides you through creating the first admin user after unlocking Jenkins.

What permission level does the first admin user have in Jenkins?

A Full administrative permissions

B Read-only access

C Build-only access

D No permissions by default

The first admin user has full administrative permissions to manage Jenkins.

If you lose the initial admin password, what can you do to regain access?

A Delete the <code>config.xml</code> and restart Jenkins

B Reinstall Jenkins

C Create a new user from the command line

D Use the Jenkins setup wizard again

Deleting config.xml resets Jenkins security, allowing you to restart and create a new admin user.

Explain the process of creating the first admin user in Jenkins after installation.

Think about the steps from opening Jenkins to having an admin account.

Describe why the initial admin password is important and where to find it.

Consider Jenkins security right after installation.

Practice

1. Why is it important to create the first admin user in Jenkins?

easy

A. To speed up the build process

B. To secure the Jenkins server by controlling access

C. To reduce the server's memory usage

D. To automatically install plugins

Solution

1. Step 1: Understand Jenkins security basics

   Jenkins requires an admin user to control who can access and manage the server.

2. Step 2: Recognize the role of the first admin user

   This user sets permissions and protects the server from unauthorized access.

3. Final Answer:

   To secure the Jenkins server by controlling access -> Option B

4. Quick Check:

   Security = Control access [OK]

Hint: First admin user controls access and security [OK]

Common Mistakes:

• Thinking admin user speeds up builds
• Confusing admin user with plugin installer
• Believing admin user reduces memory use

2. Which of the following is the correct syntax to create a new admin user using Jenkins Groovy script console?

easy

A. jenkins.createUser('admin', 'password')

B. Jenkins.instance.createUser('admin', 'password')

C. Jenkins.security.createAccount('admin', 'password')

D. jenkins.model.Jenkins.instance.securityRealm.createAccount('admin', 'password')

Solution

1. Step 1: Recall Jenkins Groovy script for user creation

   The correct method to create a user is via the securityRealm's createAccount method.

2. Step 2: Match the exact syntax

   jenkins.model.Jenkins.instance.securityRealm.createAccount('admin', 'password') is the valid syntax.

3. Final Answer:

   jenkins.model.Jenkins.instance.securityRealm.createAccount('admin', 'password') -> Option D

4. Quick Check:

   securityRealm.createAccount = correct syntax [OK]

Hint: Use securityRealm.createAccount to add users [OK]

Common Mistakes:

• Using Jenkins.instance.createUser which does not exist
• Calling jenkins.createUser directly
• Using Jenkins.security.createAccount which is invalid

3. What will be the result of running this Groovy script in Jenkins script console?

def instance = jenkins.model.Jenkins.instance
instance.securityRealm.createAccount('admin', 'admin123')

medium

A. Creates a new admin user named 'admin' with password 'admin123'

B. Throws an error because createAccount is undefined

C. Deletes the existing admin user

D. Changes the Jenkins system password

Solution

1. Step 1: Analyze the script commands

   The script gets the Jenkins instance and calls createAccount on securityRealm with username and password.

2. Step 2: Understand createAccount effect

   This method creates a new user with the given credentials in Jenkins.

3. Final Answer:

   Creates a new admin user named 'admin' with password 'admin123' -> Option A

4. Quick Check:

   createAccount adds user = Creates a new admin user named 'admin' with password 'admin123' [OK]

Hint: createAccount adds user with given name and password [OK]

Common Mistakes:

• Assuming it deletes users
• Expecting a system password change
• Thinking createAccount is undefined

4. You tried to create the first admin user with this script:

jenkins.model.Jenkins.instance.securityRealm.createAccount('admin')

Why does it fail?

medium

A. Missing password argument in createAccount method

B. Incorrect method name, should be createUser

C. Jenkins instance is not accessible in script console

D. Username 'admin' is reserved and cannot be used

Solution

1. Step 1: Check method parameters

   createAccount requires two parameters: username and password.

2. Step 2: Identify missing argument

   The script only provides username, missing the password argument, causing failure.

3. Final Answer:

   Missing password argument in createAccount method -> Option A

4. Quick Check:

   Two arguments needed = Missing password argument in createAccount method [OK]

Hint: createAccount needs username and password [OK]

Common Mistakes:

• Using wrong method name
• Assuming Jenkins instance is inaccessible
• Thinking 'admin' username is reserved

5. You want to automate creating the first admin user during Jenkins startup using an initialization Groovy script. Which approach is correct?

hard

A. Add the user credentials in config.xml directly

B. Run the createAccount command manually after Jenkins starts

C. Place a Groovy script with createAccount call in init.groovy.d directory

D. Modify Jenkins WAR file to include the user

Solution

1. Step 1: Understand Jenkins initialization scripts

   Jenkins runs Groovy scripts placed in init.groovy.d folder during startup.

2. Step 2: Automate user creation

   Placing a script with createAccount call there creates the admin user automatically on startup.

3. Final Answer:

   Place a Groovy script with createAccount call in init.groovy.d directory -> Option C

4. Quick Check:

   init.groovy.d scripts run at startup [OK]

Hint: Use init.groovy.d scripts for startup automation [OK]

Common Mistakes:

• Trying manual commands only
• Editing config.xml directly (not recommended)
• Modifying Jenkins WAR file (complex and unsafe)