I am an administrator of a team/workspace using BitBucket. We are trying to implement a repository backup tool that will periodically get a list of all team/workspace
Our tool is a bash/python script being run by a cronjob on some linux box somewhere. repositories and then download each of those repositories.
All of the documentation I have read so far indicates the requirement of authentication using a "callback" url/endpoint. Does this mean that our script is required to open a publicly accessible socket, just so the BitBucket authorization server can give our tool a token?
What about a good old API token? Those seem to have been removed. We could have a user create an app password, but we would prefer authentication not be tied to a team user account. We could create a separate user account for automation purposes, but we would rather avoid that option if possible.
What is the best method for allowing automated authentication to the BitBucket API?
