Issues Resolved

  • API Token Authentication returned 401 even with valid tokens
    • this was most likely only an issue surfacing in the latest Bitbucket versions 7.12, 7.13 or 7.14

Changes

  • REST API only: when creating a token on behalf, the user key provided in the payload is validated first.
    If it doesn't belong to a user, HTTP status 400 and a message are returned.

Documentation

To get familiar with the app, please refer to our documentation: https://wiki.resolution.de/doc/api-token-authentication/latest