Skip to content

Added support for multiple token support in bitbucket cloud #2695

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 5 commits into from
Aug 19, 2025
Merged

Added support for multiple token support in bitbucket cloud #2695

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
5 commits
Select commit Hold shift + click to select a range
b63727d
Updated docs
oiadebayo Aug 19, 2025
81e2f5d
Update _bitbucket_cloud_one_time_docker_parameters.mdx
oiadebayo Aug 19, 2025
a6b74a8
Typo correction
oiadebayo Aug 19, 2025
82febf3
Fixed grammar
oiadebayo Aug 19, 2025
df56ab5
Merge branch 'main' into Updated-bitbucket-cloud-docs-to-reflect-mult…
oiadebayo Aug 19, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion ...g/git/bitbucket/bitbucket-cloud/_bitbucket_cloud_one_time_docker_parameters.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
| Parameter | Description | Example | Required |
| ------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------- | -------- |
| `OCEAN__INTEGRATION__CONFIG__BITBUCKET_WORKSPACE_TOKEN` | The workspace token used to query authenticate with your Bitbucket Cloud account | | ✅ |
| `OCEAN__INTEGRATION__CONFIG__BITBUCKET_WORKSPACE_TOKEN` | The workspace token(s) for the Bitbucket Cloud account (can be a single token or comma-separated string of multiple tokens) | | ✅ |
| `OCEAN__INTEGRATION__CONFIG__BITBUCKET_WORKSPACE` | The workspace you want to retrieve git objects from | | ✅ |
| `OCEAN__INTEGRATION__CONFIG__BITBUCKET_USERNAME` | The username used to authenticate with your Bitbucket Cloud account | | ✅ |
| `OCEAN__INTEGRATION__CONFIG__BITBUCKET_APP_PASSWORD` | The app password used to authenticate with your Bitbucket Cloud account | | ✅ |
Expand Down
8 changes: 4 additions & 4 deletions ...ware-catalog/sync-data-to-catalog/git/bitbucket/bitbucket-cloud/installation.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -35,16 +35,16 @@ This page details how to install Port's Bitbucket Cloud integration (powered by

:::tip Use of dedicated accounts and tokens

We recommend using workspace tokens from accounts dedicated to the integration, as this will provide a more secure and scalable solution.
We recommend using multiple workspace tokens for the integration, as this will provide a more secure and scalable solution. Using multiple workspace tokens helps distribute the load and avoid rate limiting issues. You can provide multiple workspace tokens as a comma-separated string in the configuration.

Different credentials from the same Bitbucket account share the same rate limits, which can cause issues when using the integration in a large organization. Using dedicated workspace tokens helps manage rate limits more effectively.
If you are using the username and app password, we recommend using a dedicated account for the integration, as different credentials from the same Bitbucket account share the same rate limits, which can cause issues when using the integration in a large organization.
:::

The integration requires either a workspace token or an app password with username to authenticate with your Bitbucket Cloud account. You can create a workspace token by following the steps [here](https://support.atlassian.com/bitbucket-cloud/docs/workspace-access-tokens/) or an app password by following [these steps](https://support.atlassian.com/bitbucket-cloud/docs/app-passwords/).

The token or app password should have `read` permission scope for each of the supported resources you want to ingest into Port and a `read` and `write` permission scope for the webhooks.

We recommend using workspace tokens when possible, as they provide better security and are easier to manage than app passwords.
We recommend using multiple workspace tokens when possible, as they provide better security, are easier to manage than app passwords, and help avoid rate limiting issues by distributing requests across different tokens.

## Deploy the integration

Expand Down Expand Up @@ -180,7 +180,7 @@ This table summarizes the available parameters for the installation.
| `integration.config.bitbucketUsername` | The username of the Bitbucket Cloud account | ✅ |
| `integration.config.bitbucketWorkspace` | The workspace of the Bitbucket Cloud account | ✅ |
| `integration.config.bitbucketAppPassword` | The app password of the Bitbucket Cloud account | ✅ |
| `integration.config.bitbucketWorkspaceToken`| The workspace token of the Bitbucket Cloud account | ✅ |
| `integration.config.bitbucketWorkspaceToken`| The workspace token(s) for the Bitbucket Cloud account (can be a single token or comma-separated string of multiple tokens) | ✅ |
| `integration.config.webhookSecret` | The secret used to verify the webhook requests | ❌ |
| `scheduledResyncInterval` | The number of minutes between each resync | ❌ |
| `initializePortResources` | Default true, When set to true the integration will create default blueprints and the port App config Mapping | ❌ |
Expand Down
Loading