Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
badges earned

Your Points Tracker
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Two-step verification broke calling trigger-pipeline

We have a pipeline in repo A that calls another pipeline in repo B via trigger-pipeline.  This was working up until we required Two-step verification for our user accounts.

✖ Failed to initiate a pipeline. API error code: 403. Message: {"type": "error", "error": {"message": "To access this repository, enable two-step verification."}}

What can we do to fix our pipeline?

1 answer

1 accepted

0 votes
Answer accepted

Discovered that, while trigger-pipeline had previously worked with only the BITBUCKET_APP_PASSWORD defined, after requiring two-step verification for all accounts the pipeline requires also defining BITBUCKET_USERNAME.

While the app password allows us to bypass entering a one-time password (OTP) in the automated process, the user account still requires the two-step verification to be fully configured and verified before we could continue to use the trigger-pipeline function.  After assigning a pre-requisite SSH key and the MFA device to our service-user account, we generated a new App password (Personal settings > Access Management > App passwords).  We then set both the BITBUCKET_APP_PASSWORD AND BITBUCKET_USERNAME in the Repository variables.  

Once the two-step verification was fully setup and both username and app password defined in Repository variables the Pipeline is running as expected.

Suggest an answer

Log in or Sign up to answer
Community showcase
Published in Bitbucket

Calling any interview participants for Bitbucket Data Center

Hi everyone,  We are looking to learn more about development teams’ workflows and pain points, especially around DevOps, integrations, administration, scale, security, and the related challeng...

647 views 7 4
Read article

Community Events

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

Events near you