Currently we are using atlasian/trigger-pipeline plugin to trigger a custom pipeline from another repository. 2FA is enabled for all users. A specific app password is setup for this.
Example:
Repository A runs pipeline X containing two steps. First step is a 'regular' build; the 2nd one is triggering the atlasian/trigger-pipeline plugin with appropiate username and app_password in repository B (target_branch).
This was working till last week. We now get following error:
Failed to initiate a pipeline. API error code: 403. Message: {"type": "error", "error": {"message": "To access this repository, enable two-step verification."}}
Step description :
- pipe: atlassian/trigger-pipeline:4.1.7
variables:
BITBUCKET_USERNAME: $BITBUCKET_USERNAME
BITBUCKET_APP_PASSWORD: $BITBUCKET_APP_PASSWORD
REPOSITORY: 'repository-b'
BRANCH_NAME: 'target_branch'
PIPELINE_VARIABLES: > [#variables not shown]
Any idea how we can enable this setup again. It is not possible to disable 2FA. We tried recreating the app password (having access to everything) without success.
It looks like there was an update in the security policies.
Before the update you could use app passwords independently if the user has 2FA enabled. Now if the organisation requires it, you have to enable 2FA for all accounts.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.