This article explains how to set up an Backblaze B2 bucket as storage in GitProtect.
Open the Storages section and click Add storage button.
The Add storage sidebar will appear—use it to enter the name of your new storage in the Add storage name field (step 1), then click the arrow next to the Storage type section (step 2) to expand the list of available storage types.
Scroll down the list and select the Backblaze B2 option.
After selecting storage option, the system will display additional sections, including: Authentication data, Region, Bucket name, and Optional description.
Copy the key ID and application key (secret access key) from Backblaze B2, paste the key ID to the Access key ID field, and click Select or add secret access key to open the Password Manager menu and add your copied secret key to your bucket.
Click the Add new button to add your Backblaze B2 secret access key to GitProtect Password Manager. Enter a password name, then enter the application key in the New password and Confirm password fields. Click Save to finish.
Next, select the region where your bucket is created and enter the bucket name (the bucket name is the unique identifier of the container where your objects are stored) in the appropriate field.
Ensure that the browsing machine—a device with an active license and the GitProtect worker installed—can access your Backblaze bucket. To use a different device, click Change next to the Browsing machine at the bottom.
Review your settings and click the Save button to add the storage to GitProtect. Refresh the page to see the newly added storage on your storages list.
If an app key is restricted to a bucket, the listAllBucketNames permission is required for compatibility with SDKs and integrations. This permission can be enabled during creation in the web UI or via the b2_create_key API call.
As a rule, both writeFiles and deleteFiles permissions must be assigned to any key used for deleting files in the S3 compatible API.
If you want to use immutable storage, the following permissions are required:
s3:GetBucketObjectLockConfigurationconfiguration.s3:GetBucketVersioningIt must be added to the Action section, and after the changes, the section should look as shown below:
"Action": [
"s3:ListBucket",
"s3:GetObject",
"s3:PutObject",
"s3:DeleteObject",
"s3:GetBucketVersioning",
            "s3:GetBucketObjectLockConfiguration"
],
