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

If customers are ok to have password in the plain text format, here is the command to perform the initial clone that will update the URL to have the credentials. Subsequent Git operations should then proceed without asking for credentials.
 

git clone https://username:password@github.com/username/repository.git 

 here when available