nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Authorize api for bitbucket related resources

antoine.doeraene

Hello!

I can see that the forge api npm module has dedicated functions to authorize the user to jira or confluence resources (see [here](https://developer.atlassian.com/platform/forge/runtime-reference/authorize-api/)).

Is there anything similar for Bitbucket? Or any plan to add it? Typically, I have a handler in my backend that change and allow to access repository settings, but I need to check that the authenticated user can indeed do that. I will need the Bitbucket Cloud api in the meantime.

Thanks!

Comments

Caterina Curti

Hi @antoine.doeraene ,

Thanks for bringing this up. At this stage, the Authorize API is not available for Bitbucket.

Would `asUser` be an option for your use case? If not, can I ask you to add some more details for me to understand why it wouldn't work?

I'm sure you know about this already, but the difference between asApp and asUser is documented here: https://developer.atlassian.com/platform/forge/runtime-reference/product-fetch-api/#contextual-methods

I noticed requestBitbucket is missing in a few places on that page but it is available and working for Bitbucket REST API requests!

I'm not the right person to speak about the "plan to add it". I've reached out to the Forge for Bitbucket team and will share any further insight from you with them.

Thanks,
Caterina

antoine.doeraene

Hello @Caterina Curti

Thanks a lot for your answer.

The `asUser` is indeed a good pointer and we could use it, although not with its primary intent.

Our use case is that we have some settings that are tight to a repository. Let's say an api token for an external service. Only a repository administrator can update this token from the repository settings page.

We are using the bridge api to communicate between the frontend (the page) and the backend (the backend then manages that token inside the forge storage). As far as I understand, this will already ensure that the user is authenticated to bitbucket in the correct workspace, but it does not guarantee that they are administrator on the repo. What we do now is to retrieve the user account id from the context, and then we ask the Bitbucket Cloud api what privileges this account has in the repository.

So, indeed, we could use the `asUser` to make a GET request on a resource that only an administrator can have access to. If that returns 200, then we are good. But I imagine this is not the primary intent of that function.

It would be nice if we could simply do

```

import { authorize } from "@forge/api";

authorize().onRepository(repoId).isAdmin()
```

Thanks again,

Antoine

Edmund Munday

Hi @antoine.doeraene - thanks for the question!

For context, I'm the Product Manager who looks after the teams leading our Forge project. Your use-case is something I'd love to discuss with you in more detail would you be available for a 30 minute Zoom call at some point?

If so, my calendar booking link is here, please feel free to find a time that works for you and we can discuss in more detail: https://calendar.app.google/oJN4TGaT7MY5Vm8e6

antoine.doeraene

Thanks @Edmund Munday !

I'm off this week, but scheduled a call for next week. See you there.

Welcome!

It looks like you're new here. Sign in or register to get started.