All pages
Powered by GitBook
1 of 4

Loading...

Loading...

Loading...

Loading...

API limits

Rate limits are enforced for security and stability— excessive requests may block access or disrupt the application’s operation. For detailed information, refer to the .

official Bitbucket documentation

Adding Bitbucket organization to GitProtect

This article provides instructions for adding a Bitbucket organization to GitProtect.

Using OAuth

1

Log in to GitProtect Management Service, open the DevOps tab on the left side of the window, and select Bitbucket from the list.

2

Click the Connect button under Bitbucket.

3

A pop-up with Bitbucket login page will appear. Log in using your admin credentials and grant GitProtect access to the specified resources (when prompted).

4

Your Bitbucket organization has now been successfully added to GitProtect. Click Custom policy to adjust your backup policy settings, or click Run backup to execute the backup immediately using the current policy configuration.


1

Log in to GitProtect Management Service, open the DevOps tab on the left side of the window, and select Bitbucket from the list.

2

Click the advanced mode link under Bitbucket and Bitbucket DC tiles.

3

1

Log in to GitProtect Management Service, open the DevOps tab on the left side of the window, and select Bitbucket from the list.

2

Click the advanced mode link under Bitbucket and Bitbucket DC tiles.

3

When adding an organization, you may be prompted to grant additional permissions to the GitProtect application—make sure your browser allows GitProtect to open pop-up windows.

Depending on your browser, you can either adjust the settings to allow pop-ups or permit the authorization window to open once.


Set your authentication method.

  1. In Authentication, select Bitbucket.

  2. For Connect using, choose OAuth App.

  3. In the Settings section, choose whether to enable read-only mode and whether GitProtect should automatically add new repositories to your backup.

If the Read-Only Access switch is enabled, the recovery options will be disabled.

4

Configure your repository sync and default worker. Specify hours for synchronization, or set a time interval for automatic updates.

5

Click Proceed to complete adding your Bitbucket organization and grant GitProtect access to the specified resources (when prompted).

Set your authentication method.

  1. In Authentication, select Bitbucket.

  2. For Connect using, choose Username and App password.

  3. Enter your Bitbucket email address.

  4. Add or select App Password that contains your API token from the Password Manager.

  5. Choose whether GitProtect should automatically add new repositories to your backup.

4

Configure your repository sync and default worker. Specify hours for synchronization, or set a time interval for automatic updates.

5

Click Proceed to complete adding your Bitbucket organization and grant GitProtect access to the specified resources.

Using OAuth (Advanced Mode)

Using an API token

Additional browser permissions

Useful links and items

Mozilla pop-up allowance

Required permissions

Permissions required to integrate Bitbucket with GitProtect to protect its resources.

To protect a Bitbucket environment with GitProtect, the account or token used to authorize the connection must have sufficient permissions to access the workspaces, repositories, and related resources designated for backup. The specific permission scopes vary depending on the chosen authorization method.


OAuth permissions

When integrating Bitbucket using the OAuth authentication method, GitProtect requires the following permissions to securely access and protect your repository data:


Every API token created for Bitbucket integration with GitProtect requires specific permission scopes to restrict data access and define the exact operations the token can execute.

To ensure successful backup and recovery tasks, API token must be provisioned with the below required permissions.


read:pipeline:bitbucket (variables, schedules, known hosts)
  • read:workspace:bitbucket (repositories)
  • Bitbucket API token scopes

    GitProtect does not support unscoped API tokens for Bitbucket integrations.

    Applying minimal privileges may cause certain metadata (such as issues) to be omitted from the backup. Furthermore, while read-only permissions are sufficient for running backups, restoring data requires write access, which will necessitate generating a new token with elevated privileges during a recovery operation. To prevent backup omissions and ensure seamless, immediate data recovery, it is strongly recommended to select all required permissions when creating an API token for Bitbucket.

    Backup permission scopes

    Restore permission scopes

    Useful links and items

    Integration

    Required permissions
    API limits
    Adding Bitbucket organization to GitProtect
    Cover
    Cover
    Cover
    Create an API token | Bitbucket Cloud | Atlassian SupportAtlassian Support
    API tokens | Bitbucket Cloud | Atlassian SupportAtlassian Support
    Logo
    Logo