Uploaded image for project: 'Bitbucket Data Center'
  1. Bitbucket Data Center
  2. BSERV-4989

Access keys for HTTP/HTTPS


    • 6
    • We collect Bitbucket feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

      Atlassian status as of November 2021

      Hi everyone,

      Thank you for voting on this suggestion. In Bitbucket Data Center 7.18 we've added HTTP Access Tokens for projects and repositories. More details can be found in the release notes and official documentation.

      Anton Genkin
      Product Manager

      Original suggestion

      As of now, build systems like TeamCity need to retrieve the sources via SSH and a private key infrastructure in order to be secure & do not use up an additional "service user" license for each project.

      This has two major drawbacks:

      Furthermore, it forces us to enable SSH on Stash in the first place, this is not a huge drawback (due to the minimal configuration), however, still a security issue.

      Optimally we would have:

      • a default service user for each project
      • enabling the "service users" feature costs only a single user license in total (regardless of how many projects provide service users)
      • the service user can simply connect via HTTPS like all other Stash users

      (see also https://answers.atlassian.com/questions/313156/stash-licensing-for-ci-build-systems for a discussion on the topic)

            Unassigned Unassigned
            fa0095baa44e Dominik Rauch
            12 Vote for this issue
            15 Start watching this issue