In this article:
Improvements to the Git repository backup process
GitProtect allows to authenticate to more than one organization account during repositories backup. This will allow to spread the limits of sent inquiries (imposed by the service provider) over a larger number of accounts. The backup process will be accelerated and throttling will be avoided.
Additional accounts require an access token for authentication.
Where to get the password/access token for authentication?
You can generate multiple passwords/access tokens on your GitHub, GitLab, Bitbucket account. Below you will find direct links to their generation form.
- GitHub: https://github.com/settings/tokens
- GitLab: https://gitlab.com/-/profile/personal_access_tokens
- Bitbucket: https://bitbucket.org/account/settings/app-passwords/new
What permissions does GitProtect need?
The minimum permissions that allow you to authorize the GitProtect application and perform a repository backup vary depending on the service provider.
GitHub
- repo
GitLab
- read_api
- read_repository
Bitbucket
- Account: Reading
- Repositories: Reading and Admin
If you want the backup to also include metadata belonging to repositories, you need to grant more permissions.
More informations about the permissions required by GitProtect can be find here.
Adding additional accounts to authenticate to your organization
To add additional accounts for authentication, go to your Git organization's edit window.
Select Add additional Bitbucket credentials.
In the new window, select the Add new button.
Now enter your account login and add an access token in the password manager and
confirm your selection.
You can add as many accounts to your organization as you want.
Defining a backup plan that uses many users
Go to editing the selected Git plan.
Then, in the advanced settings, select the Additional git credentials option and select the accounts that you would like to use during the backup.
Finally, save your selection.