Invalid token in organization context

[dotmitsu]

Hello. I am trying to run this exporter, but get "Ivalid token" error. I get this error both on sentry.io and our sentry.

[mgrundkoetter]

As the project is used by a lot of people and I have not heard an issue like this from anyone else, I assume it is related to your project or setup of the token in sentry. Please do a curl request on the console to your sentry with the same config to verify if is not caused by a settings issue.

[bagusnl]

Hi!, I'm able to replicate the issue.
This seems to be the issue with Sentry project within an organization, as the API needs to be <Sentry_host>/api/0/organizations/{organization_slug}/projects/

Since the current documentation did not mention anything for organization slug, this seems to not be supported use case for now? Can we get confirmation on that, thank you

[mgrundkoetter]

The API docs state GET /api/0/projects/ is the correct way to retrieve the project list of all projects the token scope has access to. The docs also say the token you provide needs the project:read scope enabled to work properly. Can you make sure the token you are using has this scope?

The docs you mention need the following scopes: org:admin, org:read, org:write. This endpoint is currently not supported by this exporter. The org slug/id would be needed as input in this case. I can add this feature if you need it, here is my Amazon wishlist.

[bagusnl]

As I've mentioned earlier that the /api/0/projects/ API (at least for the Sentry's hosted version) only grabs the projects for the user itself, not as an organization (when the bearer token is generated within an organization).

Here is an example on curl response with the same Bearer token for both /api/0/projects/ and /api/0/organizations/{organization_slug}|/projects/

Generating bearer token from the user itself (token starts with sntryu_) won't grant access to the project that is within an organization, even though the user has access to said project:

As for your offering on implementing the API, I really do appreciate it. Unfortunately, I'm currently not in a financial position where I could afford it. Though, thank you