Credential storage options in Git - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

Understanding Git Credential Storage Types

Which Git credential storage option stores your credentials only in memory for a limited time?

A git-credential-plain

B git-credential-store

C git-credential-manager

D git-credential-cache

💡 Hint

Think about a storage that forgets your password after some minutes.

The git-credential-cache stores credentials temporarily in memory, usually for 15 minutes by default. The others store credentials persistently or use external helpers.

💻 Command Output

intermediate

Output of Git Credential Store Command

What is the output of the following command if the credential store file does not exist yet?

git config --global credential.helper store
cat ~/.git-credentials

A No output, the file ~/.git-credentials is created empty.

B Error: file not found ~/.git-credentials

C Outputs stored credentials in plain text

D Outputs encrypted credentials

💡 Hint

Check what happens when you enable store but have not saved any credentials yet.

The credential.helper store saves credentials in ~/.git-credentials in plain text but does not create the file until credentials are saved. Initially, the file is empty or does not exist, so cat shows nothing.

❓ Troubleshoot

advanced

Troubleshooting Git Credential Manager on Linux

You installed Git Credential Manager on Linux but Git still prompts for username and password every time. Which is the most likely cause?

A Git Credential Manager is not configured as the credential helper.

B The ~/.git-credentials file is corrupted.

C Git Credential Manager only works on Windows.

D The credential cache timeout is set to zero.

💡 Hint

Check if Git knows to use the credential manager.

If Git Credential Manager is installed but not set as the credential helper, Git will not use it and will prompt for credentials every time.

🔀 Workflow

advanced

Configuring Git to Use Credential Cache for 10 Minutes

Which command correctly sets Git to cache credentials in memory for 10 minutes?

A git config --global credential.helper 'store --timeout=600'

B git config --global credential.helper 'cache --timeout=600'

C git config --global credential.helper 'cache --timeout=60'

D git config --global credential.helper 'manager --timeout=600'

💡 Hint

Remember the cache helper uses seconds for timeout.

The cache helper stores credentials in memory and accepts a --timeout option in seconds. 600 seconds equals 10 minutes.

✅ Best Practice

expert

Choosing Secure Git Credential Storage for a Shared Workstation

You work on a shared workstation and want to store Git credentials securely without saving them in plain text files. Which credential helper is the best choice?

A git-credential-cache

B git-credential-store

C git-credential-manager-core

D No credential helper, enter credentials every time

💡 Hint

Consider helpers that integrate with OS secure storage.

git-credential-manager-core integrates with OS secure credential stores (like Windows Credential Manager, macOS Keychain, or Linux secret service), providing secure storage without plain text files. Cache stores in memory temporarily, store saves plain text files, and entering credentials every time is inconvenient.

Practice

1. Which Git credential helper stores your password temporarily in memory for a limited time?

easy

A. store

B. manager-core

C. osxkeychain

D. cache

Solution

1. Step 1: Understand credential helper types

   Git offers different helpers: cache stores credentials temporarily in memory, store saves them permanently in plain text, and platform helpers like osxkeychain or manager-core store securely.

2. Step 2: Identify temporary storage helper

   The cache helper keeps credentials in memory for a short time (default 15 minutes), so you don't have to retype passwords repeatedly during that period.

3. Final Answer:

   cache -> Option D

4. Quick Check:

   Temporary credential storage = cache [OK]

Hint: Cache means temporary memory storage for credentials [OK]

Common Mistakes:

• Confusing 'store' as temporary storage
• Thinking 'osxkeychain' is temporary
• Assuming 'manager-core' caches credentials

2. Which command correctly sets Git to use the credential helper that saves passwords permanently in plain text?

easy

A. git config --global credential.helper store

B. git config --global credential.helper cache

C. git config --global credential.helper osxkeychain

D. git config --global credential.helper manager-core

Solution

1. Step 1: Recall command syntax for setting credential helper

   The command to set a credential helper globally is git config --global credential.helper <helper-name>.

2. Step 2: Identify helper for permanent plain text storage

   The store helper saves credentials permanently in plain text on disk, so the correct command is git config --global credential.helper store.

3. Final Answer:

   git config --global credential.helper store -> Option A

4. Quick Check:

   Permanent plain text storage uses 'store' helper [OK]

Hint: Use 'store' helper for permanent plain text saving [OK]

Common Mistakes:

• Using 'cache' instead of 'store' for permanent saving
• Confusing platform helpers with plain text storage
• Missing the --global flag

3. What will be the output of the command git config --get credential.helper after running git config --global credential.helper cache?

medium

A. store

B. cache

C. osxkeychain

D. manager-core

Solution

1. Step 1: Understand the effect of setting credential helper globally

   Running git config --global credential.helper cache sets the credential helper to cache in the global Git config.

2. Step 2: Check what git config --get credential.helper returns

   This command reads the current credential helper setting, which will be cache after the previous command.

3. Final Answer:

   cache -> Option B

4. Quick Check:

   Get helper after setting cache = cache [OK]

Hint: Get command shows current helper exactly as set [OK]

Common Mistakes:

• Expecting output to be 'store' or platform helper
• Confusing local and global config scopes
• Assuming no output if helper is set

4. You set your Git credential helper with git config --global credential.helper store, but your password is still asked every time. What is the most likely cause?

medium

A. The credential helper cache is overriding store

B. The platform helper must be used instead of store

C. The stored credentials file is missing or unreadable

D. You need to restart Git after setting the helper

Solution

1. Step 1: Understand how 'store' helper works

   The 'store' helper saves credentials in a plain text file (usually ~/.git-credentials). If this file is missing or unreadable, Git cannot use stored credentials.

2. Step 2: Identify why password prompts continue

   If the credentials file is missing or has wrong permissions, Git will ask for the password every time despite the helper setting.

3. Final Answer:

   The stored credentials file is missing or unreadable -> Option C

4. Quick Check:

   Missing credentials file causes repeated password prompts [OK]

Hint: Check if credentials file exists and is readable [OK]

Common Mistakes:

• Thinking cache overrides store automatically
• Believing Git needs restart after config change
• Assuming platform helpers are mandatory

5. You want to securely store Git credentials on Windows without typing your password every time. Which credential helper should you configure?

hard

A. manager-core

B. store

C. cache

D. osxkeychain

Solution

1. Step 1: Identify platform-specific secure helpers

   On Windows, the recommended secure credential helper is manager-core, which integrates with Windows Credential Manager.

2. Step 2: Compare with other helpers

   cache is temporary, store saves plain text, and osxkeychain is for macOS, so they are not suitable for Windows secure storage.

3. Final Answer:

   manager-core -> Option A

4. Quick Check:

   Windows secure storage uses 'manager-core' helper [OK]

Hint: Use 'manager-core' for secure Windows credential storage [OK]

Common Mistakes:

• Choosing 'store' which is insecure
• Using 'osxkeychain' on Windows
• Expecting 'cache' to be secure and permanent