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.
"Atlassian Account" is a space where you can raise questions about your Atlassian Account and your identity across all of our Atlassian Cloud Products. This involves understanding User Managemen...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events