Git LFS pull with SSH Access Key breaks when two step verification required

[Zane Hooper]

Discovered the following bug today, repro steps:

1. Upgrade to a premium bitbucket account
2. Go to a repository that has Git LFS files in it > Settings > Access Keys > Add a key
3. Under Settings > Access Management > Access Controls, require 2FA
4. Try to use that access key to clone the repo

Expected result: clone repo successfully

Actual result: The SSH request to generate a JWT token works, but there is a 403 error while trying to download the relevant files from git LFS. 

[Theodora Boudale · Accepted solution]

Hi Zane,

Thank you for reporting this.

We have a bug report about this in our issue tracker:

• https://jira.atlassian.com/browse/BCLOUD-18351

Until this is fixed, a workaround would be to authenticate with a user that has access to the repo, using an app password with read-only scope.

Our development team will post an update on the bug report when this is fixed. Please note though that we don't provide ETAs and bug fixing is implemented as per our policy here.

You can add yourself as a watcher (by selecting the Start watching this issue link in the bug report) if you'd like to get notified via email on any updates. You can also select the This affects my team link to indicate you are affected by this issue.

If you have any further questions, please feel free to let me know.

Kind regards,
Theodora