Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Sourcetree Authentication failed if password contains special characters (§ and german umlauts)

We have the issue that some users are able to authenticate on Bitbucket Server using git or the weblogin, but not Sourcetree.


The error message is:

Authentication failed

Failed to check login for user [username] You do not have permission to access URL 'https://.../rest/api/1.0/users/username' please check the user credentials associated with this account. The request returned with status code 'Unauthorized'. Authentication failed. Please check your credentials and try again.


We changed the Bitbucket server back to http and checked the http-traffic.

There we see for the authentication a Base64-String containing username and password.

This is the case for git as well as for Sourcetree.


But when decoding the Sourcetree Base64-String you can see that certain characters are replaced by "?". So far this is the case for "§" as well as for german umlauts (ä,ö,ü).


As git is doing the correct encoding this seems to be a Bug in Sourcetree.

This happens with 3.4.1 as well as 3.4.6.


For us the workaround is to avoid these characters in the password.

Not sure if there is another solution. But hopefully this informations helps others who are facing the same issue.

0 answers

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events