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

The point of app passwords

I'd like to understand a bit more about the rationale for app passwords in the context of my use case.

I have a number of BitBucket repositories which I occasionally wish to interact with on random/unknown/guest machines. Currently, I can just use the HTTPS interface and type in my usual password (from memory).

Now that this has been deprecated, I am forced to use an app password which is not remotely memorable, so I am forced to store it in plaintext, and then copy and paste/print it for use on a remote machine. This obviously does not improve security at all, unless I generate a new one for each machine which is just annoying.

Why must the app passwords be auto-generated gibberish? Is there a reason I am unaware of which means it is a bad idea to have a facility to generate our own?



Log in or Sign up to comment
AUG Leaders

Atlassian Community Events