API token management in Jenkins - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to create a new API token for a Jenkins user.

Jenkins

def create_api_token(user):
    token = user.[1]('new-token')
    return token

Drag options to blanks, or click blank then click option'

AgenerateToken

BcreateToken

CnewToken

DmakeToken

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'createToken' which is not a valid Jenkins user method.

Using 'newToken' or 'makeToken' which do not exist.

The correct method to generate a new API token in Jenkins user object is generateToken.

2fill in blank

medium

Complete the code to revoke an existing API token by its name.

Jenkins

def revoke_api_token(user, token_name):
    tokens = user.getApiTokens()
    tokens.[1](token_name)
    user.save()

Drag options to blanks, or click blank then click option'

AremoveToken

BdeleteToken

CrevokeToken

DclearToken

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'removeToken' which is not a Jenkins API method.

Using 'revokeToken' or 'clearToken' which do not exist.

The method to delete an API token by name in Jenkins is deleteToken.

3fill in blank

hard

Fix the error in the code to list all API tokens for a Jenkins user.

Jenkins

def list_tokens(user):
    tokens = user.[1]()
    for token in tokens:
        print(token.name)

Drag options to blanks, or click blank then click option'

AfetchTokens

BlistTokens

CretrieveTokens

DgetApiTokens

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'listTokens' which is not a valid method.

Using 'fetchTokens' or 'retrieveTokens' which do not exist.

The correct method to get all API tokens from a Jenkins user is getApiTokens.

4fill in blank

hard

Fill both blanks to check if a token exists and then revoke it.

Jenkins

def revoke_if_exists(user, token_name):
    tokens = user.getApiTokens()
    if token_name [1] tokens:
        tokens.[2](token_name)
        user.save()

Drag options to blanks, or click blank then click option'

Ain

Bnot in

CdeleteToken

DremoveToken

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'not in' instead of 'in' for the check.

Using 'removeToken' which is not a valid method.

Use in to check if the token exists, then deleteToken to revoke it.

5fill in blank

hard

Fill all three blanks to create a token, print its value, and save the user.

Jenkins

def create_and_show_token(user, token_name):
    token = user.[1](token_name)
    print(token.[2])
    user.[3]()

Drag options to blanks, or click blank then click option'

AgenerateToken

Bvalue

Csave

DtokenValue

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'tokenValue' instead of 'value' property.

Forgetting to call 'save' on the user.

Use generateToken to create, value to get the token string, and save to persist changes.

Practice

1. What is the main purpose of an API token in Jenkins?

easy

A. To allow secure access to Jenkins without using your password

B. To reset your Jenkins user password automatically

C. To create new Jenkins user accounts

D. To monitor Jenkins server performance

Solution

1. Step 1: Understand API token function

   An API token acts like a password substitute for accessing Jenkins securely.

2. Step 2: Compare options

   Only To allow secure access to Jenkins without using your password correctly describes the token's purpose; others describe unrelated functions.

3. Final Answer:

   To allow secure access to Jenkins without using your password -> Option A

4. Quick Check:

   API token = secure password substitute [OK]

Hint: API tokens replace passwords for safe Jenkins access [OK]

Common Mistakes:

• Thinking tokens reset passwords
• Confusing tokens with user creation
• Assuming tokens monitor performance

2. Which Jenkins menu path lets you create a new API token?

easy

A. Manage Jenkins > Configure System

B. Dashboard > New Item

C. User Profile > Configure > API Token

D. Manage Plugins > Available

Solution

1. Step 1: Locate API token creation

   API tokens are created in the user's own profile settings, not global or plugin menus.

2. Step 2: Match correct menu path

   Only User Profile > Configure > API Token correctly points to User Profile > Configure > API Token.

3. Final Answer:

   User Profile > Configure > API Token -> Option C

4. Quick Check:

   API tokens created in user profile [OK]

Hint: API tokens are in your user profile settings [OK]

Common Mistakes:

• Looking under Manage Jenkins instead of user profile
• Confusing plugin menus with token creation
• Trying to create tokens from dashboard

3. What will happen if you use an invalid API token in a Jenkins REST API call?

medium

A. The API call succeeds but with limited permissions

B. The API call fails with an authentication error

C. The API call triggers a password reset

D. The API call is queued for later processing

Solution

1. Step 1: Understand token validation

   Jenkins checks API tokens for validity before allowing access.

2. Step 2: Identify failure behavior

   Invalid tokens cause authentication failure, so the call is rejected.

3. Final Answer:

   The API call fails with an authentication error -> Option B

4. Quick Check:

   Invalid token = authentication error [OK]

Hint: Invalid tokens cause authentication errors [OK]

Common Mistakes:

• Assuming calls succeed with limited access
• Thinking invalid tokens reset passwords
• Believing calls queue instead of failing

4. You created an API token but Jenkins shows 'Invalid token' error when using it. What is the most likely cause?

medium

A. You copied the token incorrectly or partially

B. You used the token in the Jenkins UI instead of API calls

C. You created the token in the wrong Jenkins instance

D. You forgot to restart Jenkins after creating the token

Solution

1. Step 1: Check token usage errors

   Common error is copying the token incorrectly, causing invalid token errors.

2. Step 2: Evaluate other options

   Tokens work immediately without restart; UI usage is different; wrong instance is less common.

3. Final Answer:

   You copied the token incorrectly or partially -> Option A

4. Quick Check:

   Copy error = invalid token [OK]

Hint: Always copy API tokens fully and exactly [OK]

Common Mistakes:

• Restarting Jenkins unnecessarily
• Using tokens in UI login fields
• Ignoring token instance mismatch

5. You want to revoke an old API token without affecting other tokens. How do you do this safely in Jenkins?

hard

A. Disable your Jenkins user account temporarily

B. Change your Jenkins user password to invalidate all tokens

C. Restart Jenkins to clear all active tokens

D. Delete the specific token from your user profile's API token list

Solution

1. Step 1: Understand token revocation

   Jenkins allows deleting individual API tokens from your user profile without affecting others.

2. Step 2: Compare other methods

   Changing password invalidates all tokens; restarting Jenkins or disabling account are not selective.

3. Final Answer:

   Delete the specific token from your user profile's API token list -> Option D

4. Quick Check:

   Delete token individually to revoke safely [OK]

Hint: Revoke tokens individually via user profile [OK]

Common Mistakes:

• Changing password to revoke one token
• Restarting Jenkins unnecessarily
• Disabling user instead of token