Using new API Tokens in pipelines

[victoryaremko]

I am using a Bitbucket pipeline to trigger another one.

Here is my current configuration:

- pipe: atlassian/trigger-pipeline:4.3.1

     variables:

         BITBUCKET_USERNAME: $BITBUCKET_USERNAME

         BITBUCKET_APP_PASSWORD: $BITBUCKET_APP_PASSWORD

         REPOSITORY: 'my-repo'

         BRANCH_NAME: 'master'

         ACCOUNT: 'my_account'

         PIPELINE_VARIABLES: >

            [{

                "key": "EXTENSION_ID",

                 "value": "$EXTENSION_ID",

              }]

Since app passwords are becoming obsolete, I would like to integrate API tokens into my process, but I am running into problems.

My current approach no longer works — the pipeline fails with:
 

✖ Authentication missing. You must provide an access token or an Atlassian email and Atlassian API token.

I have tried using an API token instead of an app password, and my email instead of the username, but with no luck. The suggested solution from your AI chatbot to use API_TOKEN and BITBUCKET_EMAIL variables gives me the same result.

Could you provide some guidance on how I should modify my pipeline code to make it work with API tokens?

[victoryaremko · Accepted solution]

I was able to manage the issue by using the following params

- pipe: atlassian/trigger-pipeline:5.10.1

              variables:

                ATLASSIAN_ACCOUNT_EMAIL: $ATLASSIAN_ACCOUNT_EMAIL

                ATLASSIAN_API_TOKEN: $ATLASSIAN_API_TOKEN

                REPOSITORY: "'my-repo"

                REF_TYPE: "branch"

                REF_NAME: "master"

                ACCOUNT: "my_account"

in repository variables i have provided :
- ATLASSIAN_ACCOUNT_EMAIL (my account email)
- ATLASSIAN_API_TOKEN (generated here)