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
Next: Root
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
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
https://confluence.atlassian.com/cloud/api-tokens-938839638.html
We're following the documentation above. When we create an api token, will basic authentication with password be immediately disabled? My company needs basic authentication to work or else we're scrambling with repairing a bunch of automation we have set up.
Hi Kevin, welcome to the Atlassian Community.
Think about these API tokens as additional (alternative) passwords for an account. The Curl example in that documentation also includes the username but replaces the password with the token. When you enable one token, you can continue to authenticate with your main password.
As a best-practice advice, we do not recommend to have automation running with your main password. In fact, you can create as many API tokens as you want, and we recommend that you use one for every automation. This way, you can have a very granular control, as you can give names to the tokens and revoke each one whenever you want.
Claudiu
Thank you. Will be working on this.
Will enable the token first and change the setup. If everything works, we're a-ok.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.