Issue Summary

Currently Bitbucket API Token length is higher and not supported by Git Credential Manager on Windows platform.

When user use the Git Credential Manager to store the Git credentials (User name and API Token), the credentials seems to be stored in Windows Credential Manager but not stored correctly.

When the user perform the subsequent Git operation, Git asks for the Git credentials even they have been stored as they are not stored correctly.

Steps to Reproduce

1. Setup Git Credential Manager on windows
2. Perform Git operation
3. Git asks for the credentials
4. Credentials stored into Windows Credential Managers in Windows Credentials tab
5. Perform another Git operation

Expected Results

Git shouldn't ask for the credentials

Actual Results

Git asks for the credentials

Workaround

Ensure GCM is configured to use Bitbucket “basic” auth (username + API token):

git config --global credential.bitbucketAuthModes "basic"

Disable stored-credential validation to avoid repeated prompts on Windows:

git config --global credential.bitbucketValidateStoredCredentials false

(Then store the credential once via a Git operation; subsequent operations should re-use the Windows Credential Manager entry without prompting.)