This article explains how to prepare and add additional Bitbucket accounts to GitProtect in order to prevent throttling.
GitProtect allows authentication with multiple organization accounts during repository backups. This helps distributing the limits of sent requests (imposed by the service provider) across more accounts, which speeds up the backup process and prevents throttling.
To add additional accounts for authentication to your Bitbucket organization, log in to your Bitbucket account and add a member to your workspace. The user should belong to a group with an Admin role for repositories, and also have the Administer workspace (Can administer all workspace and repository settings) option selected.
💡 Learn more about workspace access in the official Bitbucket documentation.
You can generate multiple app passwords in the App passwords tab of your Bitbucket account. The minimum permissions required to authorize the GitProtect application to perform a repository backup are:
Login to GitProtect Management Service and open the Bitbucket tab (DevOps > Bitbucket). Find your Bitbucket repository and click Edit in the bottom-left corner of the selected tile.
Go to the Additional credentials section and click it.
In GitProtect Management Service, open the Plans tab and click Add plan, or select Edit plan if you already have one.
Scroll down to Advanced settings, click Edit, and enable the Additional git credentials switch.
Click the Add new button, enter the credentials, and then click Save to finish.
The system will display all additional accounts available for the selected organization. Toggle the switch ON next to the accounts you want to use, and then click the Save button.
Back in the Edit backup plan panel, click the Save button to save your backup plan settings. The backup plan will now run using the selected additional Bitbucket accounts.
This article provides general information about the throttling prevention mechanism and how GitProtect uses credential rotation to ensure task continuity.
GitProtect implements a credential management system that optimizes API limit usage by distributing requests across multiple accounts or access tokens. This process occurs automatically on two levels.
Every task (backup or restore) launched in the system is assigned credentials from an available pool. The system applies a rotation principle, meaning that subsequent tasks use different authentication data (e.g., task A uses credential a, task B uses credential b, and so on). This ensures that API limits are used evenly, significantly reducing the likelihood of being blocked.
If throttling occurs during an active task, the Management Service takes the following steps:
Available additional credentials — if other credentials are available in the pool, Management Service sends new credentials to the worker. The task continues without interrupting the operation.
No additional credentials available — if the credential pool is exhausted, Management Service informs the worker that no more credentials are available. The task is then suspended and marked as Throttled, waiting for the limits to reset.
For the credential exchange mechanism to function correctly during operations, specific permission requirements must be met:
This article explains how to prepare and add additional Bitbucket DC accounts to GitProtect in order to prevent throttling.
In Bitbucket DC, you can create user accounts and organize them into groups. This makes it easier to manage the organization and permissions.
💡 Learn more about users and groups in the official Bitbucket DC documentation.
Click your profile picture and go to Manage account > HTTP access tokens.
Select Create token.
Set the token name, permissions, and expiry.
💡 Learn more about HTTP access tokens in official .
Login to GitProtect Management Service and open the Bitbucket tab (DevOps > Bitbucket). Find your Bitbucket DC project (this must be done for each project individually) and click Edit in the bottom-left corner of the project tile.
Go to the Additional credentials section and click it.
In GitProtect Management Service, open the Plans tab and click Add plan, or select Edit plan if you already have one.
Scroll down to Advanced settings, click Edit, and enable the Additional git credentials switch.
Click the Add new button, enter the credentials, and then click Save to finish.
The system will display all additional accounts available for the selected organization. Toggle the switch ON next to the accounts you want to use, and then click the Save button.
Back in the Edit backup plan panel, click the Save button to save your backup plan settings. The backup plan will now run using the selected additional Bitbucket DC accounts.
This article explains how to prepare and add additional GitHub and GitHub Enterprise credentials to GitProtect in order to prevent throttling.
You can add anyone to your GitHub (or GitHub Enterprise) organization, and they will become a member. To do this, follow the instructions on the official GitHub page.
In the upper-right corner of any page, click your profile photo and select Settings.
In the left sidebar, click Developer settings.
Select Personal access tokens.
Click Generate new token.
Enter a descriptive name for the token.
Login to GitProtect Management Service, open the GitHub tab (DevOps > GitHub) and click Edit in the bottom-left corner of your GitHub organization tile.
Go to the Throttling prevention section and click Manage credentials.
In GitProtect Management Service, open the Plans tab and click Add plan, or select Edit plan if you already have one.
Scroll down to Advanced settings, click Edit, and enable the Additional git credentials switch.
Click the Add new button and select one of the available options:
For Access Token:
Enter your account username and add or select PAT from the Password Manager, then confirm your selection. You can add any number of accounts to your organization.
For GitHub App:
From the drop-down list, select an application (#1–#10) and install it in the appropriate organization. The process is the same as when adding the main GitHub app.
IMPORTANT! You can add an additional GitHub App only if the following conditions are met:
The installing account has sufficient permissions on GitHub—the installation must not require sending and approving an installation request (it may happen, for example, when the account lacks repository administration rights or has a role other than Owner in an organization). For more details, see *.
The organization in GitProtect system has the main credentials for the GitHub account where the additional GitHub App is being installed**:
If the organization was registered through a GitHub App, additional GitHub Apps can only be added for accounts that already have the main GitHub App registered. Additional GitHub App for other personal accounts are not allowed.
If the organization was registered through OAuth or a PAT, additional GitHub App
The system will display all additional accounts available for the selected organization. Toggle the switch ON next to the accounts you want to use, and then click the Save button.
Back in the Edit backup plan panel, click the Save button to save your backup plan settings. The backup plan will now run using the selected additional GitHub (or GitHub Enterprise) accounts.
This article explains how to prepare and add additional GitLab accounts to GitProtect in order to prevent throttling.
The best way to add an additional account to your GitLab environment is by adding a new user to the dedicated group. This way, the added user automatically gains access to all projects within the group.
Alternatively, you can add a user to individual projects separately.
💡 For detailed information about organization membership, see the official GitLab documentation.
Login to GitProtect Management Service, open the GitLab tab (DevOps > GitLab) and click Edit in the bottom-left corner of the selected GitLab repository tile.
Go to the Additional credentials section and click it.
Click the Add new button, enter the credentials, and then click Save to finish.
In GitProtect Management Service, open the Plans tab and click Add plan, or select Edit plan if you already have one.
Scroll down to Advanced settings, click Edit, and enable the Additional git credentials switch.
The system will display all additional accounts available for the selected organization. Toggle the switch ON next to the accounts you want to use, and then click the Save button.
Back in the Edit backup plan panel, click the Save button to save your backup plan settings. The backup plan will now run using the selected additional GitLab accounts.
