After changing authentication to API Token, I cannot clone existing repositories

[jeffrey_a_king]

On Bitbucket repository web page:
- I click on Clone, then change from SSH to HTTPS

- Click on Clone in Sourcetree

- Sourcetree shows https://my_user_name@bitbucket.org/repository_name
   and reports "This is not a valid source path / URL" and will not allow clone

- Tried changing to https://my_email_address@bitbucket.org/repository_name
   still reports as not valid and cannot clone

- Repositories that had been previously cloned function normally

[Tomislav Tobijas]

Hey @jeffrey_a_king ,

Can you check this troubleshooting article and try the steps defined there: Troubleshooting Bitbucket Git issues 

Also, can you check your Windows Credential manager? You can see a few details about that here: https://community.atlassian.com/forums/Sourcetree-questions/Bitbucket-with-API-tokens-yet-again/qaa-p/3195923#M46947

Also, which Sourcetree version are you using? If you're not on the latest one, I'd suggest upgrading 👉 Sourcetree / Download archives 

Cheers,
Tobi

[jeffrey_a_king]

Thank you Tomislav.

I didn't get anything from the Bitbucket Git issues article.

In Credential Manager, I re-entered the API token for the password for the two entries marked in red:

From the "Bitbucket with API tokens! (yet again)" titled question, I performed the terminal commands shown:

Trying to clone from Sourcetree, here are the Details I get now:

Using 3.4.30 of Sourcetree.

[jeffrey_a_king]

[jeffrey_a_king]

- I deleted all sourcetree-rest entries in Windows Credential Manager

- same as Alastair Murray in Bitbucket with API tokens! (yet again), "my account on the 'remote repo' screen was broken (red glyph) until I reauthorised with user name and API token (I also tried email but that didn't work)"

- opened the Sourcetree console and performed:
git config --global credential.helper core
git config --system credential.helper core

- the CredentialHelperSelector dialog wouldn't accept <no helper> in my case. It would only accept <windows cred>

- Account is authorized:

- I now receive this when I try to clone a remote repository:

- Snooping around in Tools > Options > Git, I see manage credentials via the Git Credential Manager is checked. It doesn't seem correct, should this be checked?:

[jeffrey_a_king]

I am able to clone using the Sourcepass console using HTTPS:

Again, it shows that 'credential-core' is not a git command. But with the console, the clone succeeded.

[jeffrey_a_king]

Found .gitconfig file, here's what it shows:

[jeffrey_a_king]

Shouldn't this just work? Atlassian is forcing the change from passwords to API tokens. It's beginning to look like I'm going to have to spend my evenings cloning 20+ repositories with the console before I possibly lose access on June 6th, D-Day...

[jeffrey_a_king]

In .gitconfig, I changed [credential] helper from core to wincred, restarted Sourcetree, and now clone works!!!:

Well, that was lost hours of fun... hope this anxiety-induced mess helps someone.

[Tomislav Tobijas]

Oh, nice @jeffrey_a_king !! Thanks for sharing these steps and the final resolution to your problem. Definitely going to bookmark this (at least for myself) 🙂

Btw, apologies for the delayed response from my side - I'm currently OOO, so I'm struggling with catching all emails and notifications that arrive in my inbox 😅

[jeffrey_a_king]

No problem, I understand. Your post got me looking at Windows Credential Manager and areas of Git I haven't seen before.

I don't know if I can say I learned anything, it was all driven by the fear of not being able to access our lesser-used repos. I just tried to record things I found and tried.

I still don't know why one answer was to set the credential helper to core. On the Git credential helpers page, core is not an option. That's when I tried wincred: