Can not Authenticate using Team API key (BB-12972)

Issue #11325 wontfix
Creepers Help
created an issue

When trying to authenticate via Team Name as user and Team API key as password I can not create issues. The response is

HTTP/1.1 403 FORBIDDEN

ETag:
    "0a881bb6dc36feebc11d878212174da2"
Content-Language:
    en
X-Render-Time:
    0.0370140075684
Content-Length:
    70
X-Served-By:
    app16
X-Version:
    05e6f80709ec
Connection:
    keep-alive
X-Request-Count:
    384
Server:
    nginx/1.6.2
X-Frame-Options:
    SAMEORIGIN
Date:
    Sat, 09 May 2015 20:25:55 GMT
Vary:
    Authorization, Accept-Language, Cookie
X-Static-Version:
    753bdf2dcfcf
Content-Type:
    text/plain; charset=utf-8


You must confirm your email address before creating or editing issues.

Thank you for reviewing this.

Comments (11)

  1. Jesse Yowell staff

    After speaking with the development team, this is by design -- we want to dissuade people from using the team as a user with an API key, as we don't want to treat teams as users any longer (hence the the reason we removed login access as a team). I do admit this is a bit confusing, as we should probably be returning a '405 (Method Not Allowed)' instead of a '403 (Forbidden)'

  2. Justin Pye

    So what this the equivalent of Github's personal access tokens? If not do you offer something similar. Oauth2 is pretty horrible when trying to write automation via command line executions.

  3. Sam Stickland

    Umm.. yes, if this doesn't work anymore how do I configure my Rails app to use private bitbucket hosted gems?

    This is the sort of thing that will be pushing me to github very quickly!

  4. Ivan Overgard

    Is there an equivalent to this feature that works well from the command line? I'm trying to install packages from the command line using npm, and the packages will be shared with the team. I'd like to just have a token i can put in my package.json, rather than installing credentials on around 20 workstations. Many members of my team aren't familiar with git so asking them to set up ssh keys would be difficult.

  5. Log in to comment