Repository list is not filled when using API token and user has only Read Only access

ExportXMLWordPrintable

    • 937.3.5

       

      According to https://www.atlassian.com/blog/bitbucket/bitbucket-cloud-transitions-to-api-tokens-enhancing-security-with-app-password-deprecation

       

      User API token must be used but it seems to not managed correctly by Bitbucket Branch Source plugin...

       

      When editing a multibranch pipeline, the dropdown with list of repositories is not filled.

      According to documentation (https://github.com/jenkinsci/bitbucket-branch-source-plugin/blob/master/docs/USER_GUIDE.adoc#user-api-token-bitbucket-cloud-only), API token required only read access but it seems that Bitbucket user on which API token is created must have write access to repositories to be listed...

       

      Previously, with app password authentication, only read access were mandatory.

      Could you please fix this regression ?

       

            Assignee:
            Nikolas Falco
            Reporter:
            Robin
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: