You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
I received an email warning from Atlassian that user passwords won't be allowed after March 1. I followed the steps at this page to create an app password and apply it to Sourcetree (v. 3.4.7):
I granted almost all permissions to the app password, except account/issues/wiki.
When I try to edit or add an authentication account in Sourcetree, it spins a bit and displays the error message: 'Your credentials lack one or more required privilege scopes'. I've tried both HTTPS and SSH, using Basic authentication. If I use my user password, it works fine (but of course that apparently won't work after March).
I tried once again creating a new app password, and this time I gave it EVERY permission available. I used the password to create a new authentication login in Sourcetree, and this time it worked. I don't know whether adding the user-account permissions etc. actually made a difference, or if something was different with how Sourcetree connected with the Atlassian system. But it's annoying that it seems that I had to give it such broad permissions in order to get it to work.
I had included read/write on repositories in a prior app password, but it didn't work for me--I got the notice that it lacked privileges. That said, per my other post here, when I granted all available permissions it worked, but the extra ones I added should not have made a difference. So I'm still befuddled about why it worked with all permissions.