Two-step verification broke calling trigger-pipeline

[Matt Hill]

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?

[Matt Hill · Accepted solution]

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.