[JENKINS-72212] DPAPI credential store (on Windows) leads to "fatal: Cannot prompt because user interactivity has been disabled."

[jenkins-infra-bot]

Due to known incompatibility between SSH connectivity to agents and the Windows Credentials Manager (wincredman) – see https://github.com/git-ecosystem/git-credential-manager/blob/main/docs/credstores.md#windows-credential-manager – I attempted to switch to using the DPAPI credential store as recommended. However, that results in this error when using withCredentials with a gitUsernamePassword username+password credential specified:

fatal: Cannot prompt because user interactivity has been disabled.

I've been able to use this same credential successfully with this same approach on Linux agents (also connected via SSH) with their default Git credential store on Linux (which is neither wincredman nor DPAPI), so am assuming it's not an issue with the credential itself.

Is this error a bug/incompatibility between the Credentials Binding plugin and the use of DPAPI? I got the same error in attempting to use the "plaintext" credential store as well.

---

Originally reported by medianick, imported from: DPAPI credential store (on Windows) leads to "fatal: Cannot prompt because user interactivity has been disabled."

• status: Open
• priority: Minor
• component(s): credentials-binding-plugin
• resolution: Unresolved
• votes: 0
• watchers: 2
• imported: 20251211-141027

Raw content of original issue

Due to known incompatibility between SSH connectivity to agents and the Windows Credentials Manager (wincredman) – see https://github.com/git-ecosystem/git-credential-manager/blob/main/docs/credstores.md#windows-credential-manager – I attempted to switch to using the DPAPI credential store as recommended. However, that results in this error when using withCredentials with a gitUsernamePassword username+password credential specified:


fatal: Cannot prompt because user interactivity has been disabled.


I've been able to use this same credential successfully with this same approach on Linux agents (also connected via SSH) with their default Git credential store on Linux (which is neither wincredman nor DPAPI), so am assuming it's not an issue with the credential itself.
Is this error a bug/incompatibility between the Credentials Binding plugin and the use of DPAPI? I got the same error in attempting to use the "plaintext" credential store as well.

• environment: Windows agent connected to via SSH

[jenkins-infra-bot]

markewaite:

• Original comment link
• Raw content of original comment:

  I'm not aware of anyone testing the Windows DPAPI credential store with Jenkins credentials binding plugin.  I know that I have not tested it with the git plugin and don't have any plans to test it with the git plugin.
  

I'm not aware of anyone testing the Windows DPAPI credential store with Jenkins credentials binding plugin. I know that I have not tested it with the git plugin and don't have any plans to test it with the git plugin.

[jenkins-infra-bot]

medianick:

• Original comment link
• Raw content of original comment:

  That’s fair. I do intend to switch these builds to a Linux agent once I can work out the other dependencies, so this problem will solve itself that way.
  
  It was interesting to note that the plaintext option (cross-platform) exhibits the same behavior, although I have no intent to use that due to its security issues.
  

That’s fair. I do intend to switch these builds to a Linux agent once I can work out the other dependencies, so this problem will solve itself that way.

It was interesting to note that the plaintext option (cross-platform) exhibits the same behavior, although I have no intent to use that due to its security issues.