-
Type:
Suggestion
-
Resolution: Unresolved
-
Component/s: API Framework - Access Tokens
-
None
-
1
Problem definition
Rovo agents created in Rovo Studio can't use the built-in Bitbucket skills against Bitbucket Cloud. Actions such as searching repositories, getting workspace permissions, reading files, listing branches or creating pull requests fail with 401 Unauthorized. This happens in both of the agent's authentication modes:
- User, where the agent acts on behalf of the signed-in user
- Agent account, where the agent acts as its own identity
The same agent can run Jira actions successfully, and users have full access to the Bitbucket workspace and repositories. Bitbucket Cloud doesn't currently accept the credentials Rovo agents use to call Bitbucket on a user's behalf or as an agent account.
Suggested solution
Let Bitbucket Cloud accept requests from Rovo agents in both modes:
- User mode: the agent acts on behalf of the user and follows that user's Bitbucket workspace and repository permissions.
- Agent account mode: the agent account can be granted Bitbucket workspace and repository permissions through normal admin group and role management, with no manual provisioning per account.
Workaround
Use Rovo Dev, which connects to Bitbucket Cloud separately and can read repositories and create pull requests.
- blocks
-
PCS-3877331 Loading...