Credential scoping (global, folder) in Jenkins - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is credential scoping in Jenkins?

Credential scoping in Jenkins means deciding where a credential can be used, such as globally across all jobs or limited to a specific folder.

beginner

What does 'global' scope mean for Jenkins credentials?

Global scope means the credential is available to all jobs and folders in the Jenkins instance.

intermediate

What is the benefit of using folder-scoped credentials in Jenkins?

Folder-scoped credentials limit access to only jobs inside that folder, improving security by restricting credential use.

intermediate

How do you create a folder-scoped credential in Jenkins?

Go to the folder, click 'Credentials', then add a new credential. It will be scoped only to that folder and its subfolders.

beginner

Can a folder-scoped credential be used outside its folder in Jenkins?

No, folder-scoped credentials are only accessible within the folder they belong to and its subfolders.

What does a global credential scope in Jenkins allow?

A Access to all jobs and folders

B Access only to one job

C Access only to one folder

D No access to any job

Global scope means the credential is available to all jobs and folders in Jenkins.

Where can folder-scoped credentials be used in Jenkins?

A Anywhere in Jenkins

B Only inside the folder and its subfolders

C Only in the global folder

D Only in other folders

Folder-scoped credentials are limited to the folder they belong to and its subfolders.

Why use folder-scoped credentials instead of global ones?

A To delete credentials automatically

B To make credentials available everywhere

C To improve security by limiting access

D To share credentials with other Jenkins instances

Folder-scoped credentials restrict access, improving security by limiting where credentials can be used.

How do you add a credential scoped to a folder in Jenkins?

A Add it inside the folder's Credentials section

B Add it in the global Jenkins credentials

C Add it in the system configuration

D Add it in the job configuration

Adding credentials inside a folder's Credentials section scopes them to that folder.

If a credential is global, can it be used in a folder job?

A Only if the job is admin

B No, global credentials are restricted

C Only if the folder allows it

D Yes, global credentials are accessible everywhere

Global credentials are accessible to all jobs, including those in folders.

Explain the difference between global and folder-scoped credentials in Jenkins.

Think about who can use the credential depending on where it is stored.

Describe how to create and use a folder-scoped credential in Jenkins.

Focus on the steps inside the folder context.

Practice

1. What does Global credential scope mean in Jenkins?

easy

A. The credential can be used by any job in Jenkins.

B. The credential is only available to jobs in a specific folder.

C. The credential is only available to the Jenkins administrator.

D. The credential expires after one use.

Solution

1. Step 1: Understand credential scopes

   Global scope means credentials are accessible everywhere in Jenkins.

2. Step 2: Compare with folder scope

   Folder scope limits credentials to jobs inside that folder only.

3. Final Answer:

   The credential can be used by any job in Jenkins. -> Option A

4. Quick Check:

   Global scope = accessible to all jobs [OK]

Hint: Global means all jobs can use it, no folder limits [OK]

Common Mistakes:

• Confusing global with folder scope
• Thinking global is admin-only
• Assuming credentials expire automatically

2. Which of the following is the correct way to assign a credential to a folder in Jenkins?

easy

A. Add the credential under Jenkins > Credentials > System > Global credentials

B. Add the credential inside the folder's Credentials section

C. Add the credential in the job configuration only

D. Add the credential in Jenkins > Manage Plugins

Solution

1. Step 1: Locate folder credentials

   Folder scoped credentials are added inside the folder's own Credentials section.

2. Step 2: Differentiate from global credentials

   Global credentials are added under Jenkins system credentials, not folder.

3. Final Answer:

   Add the credential inside the folder's Credentials section -> Option B

4. Quick Check:

   Folder credentials go inside folder settings [OK]

Hint: Folder credentials must be added inside that folder [OK]

Common Mistakes:

• Adding folder credentials to global system store
• Trying to add credentials in job config only
• Confusing plugin management with credentials

3. Given a folder named ProjectA with a credential scoped to it, what happens if a job outside ProjectA tries to use that credential?

medium

A. The job can use the credential without restrictions.

B. The job will use a default global credential instead.

C. The job will fail to access the credential.

D. The job will prompt the user to enter the credential manually.

Solution

1. Step 1: Understand folder scope restrictions

   Folder scoped credentials are only accessible to jobs inside that folder.

2. Step 2: Check job location

   A job outside the folder cannot access folder-scoped credentials.

3. Final Answer:

   The job will fail to access the credential. -> Option C

4. Quick Check:

   Folder scope blocks jobs outside folder [OK]

Hint: Folder credentials block jobs outside folder [OK]

Common Mistakes:

• Assuming folder credentials are global
• Thinking Jenkins auto-fills missing credentials
• Believing jobs can prompt for credentials

4. You added a credential to a folder but jobs inside the folder still cannot access it. What is the most likely cause?

medium

A. The folder permissions prevent jobs from using credentials.

B. The jobs are not inside the folder where the credential was added.

C. The credential was added with global scope instead of folder scope.

D. The credential type is unsupported by Jenkins.

Solution

1. Step 1: Verify credential scope

   If credential is in folder, scope is correct; global scope would make it accessible everywhere.

2. Step 2: Check folder permissions

   Folder permissions can restrict job access to credentials even if scope is correct.

3. Final Answer:

   The folder permissions prevent jobs from using credentials. -> Option A

4. Quick Check:

   Permissions can block credential use inside folder [OK]

Hint: Check folder permissions if folder credentials fail [OK]

Common Mistakes:

• Assuming scope is wrong without checking permissions
• Ignoring folder membership of jobs
• Thinking Jenkins blocks unsupported credential types silently

5. You want to restrict a credential so only jobs in the DevOps folder and its subfolders can use it, but not jobs elsewhere. How should you configure the credential?

hard

A. Add the credential in each job configuration inside DevOps.

B. Add the credential with global scope and restrict job permissions manually.

C. Add the credential with system scope to limit access.

D. Add the credential with folder scope inside the DevOps folder.

Solution

1. Step 1: Understand folder scope for restriction

   Folder scope limits credential use to jobs inside that folder and its subfolders.

2. Step 2: Avoid global or system scope

   Global scope allows all jobs; system scope is not a valid Jenkins credential scope.

3. Step 3: Avoid per-job credentials for manageability

   Adding credentials per job is inefficient and error-prone.

4. Final Answer:

   Add the credential with folder scope inside the DevOps folder. -> Option D

5. Quick Check:

   Folder scope limits credential to folder and subfolders [OK]

Hint: Use folder scope inside DevOps folder for restriction [OK]

Common Mistakes:

• Using global scope and relying on permissions only
• Confusing system scope with folder scope
• Adding credentials individually to jobs