The Atlassian Community Forums are currently in read-only mode. We will be relaunching on a new platform on September 22 (read more here). We apologize for the extended downtime. For concerns or questions, please email communitymanagers@atlassian.com. See you on the other side, on the new Atlassian Community Forums! :)

×

Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Will enabling API Tokens immediately disable basic authentication?

Kevin Chen
July 16, 2018

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.

1 answer

1 accepted

Comments for this post are closed

Community moderators have prevented the ability to post new answers.

0 votes
Answer accepted
Deleted user
July 17, 2018

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

Kevin Chen
July 17, 2018

Thank you.  Will be working on this.

 

Will enable the token first and change the setup.  If everything works, we're a-ok.

TAGS
AUG Leaders

Atlassian Community Events