Get issuetype avatar by id using auth other than basic

Hello!

I was wondering if there’s any way to get an avatar image by id with something other than the Basic authentication used in the example used here. For the “public” avatars we have no issue, but for the project specific ones etc, this becomes an issue.

We can get it using that authentication but there’re situations where we might not have access to the user’s email (because it’s private) and we wouldn’t like to make the request as app… Does anyone have some insight on this? Some kind of workaround?

Thanks in advance,
Paulo Mendes

Hello @PauloMendes

For Basic auth, the user who owns the key / token must have Browse Project permissions for at least one Project that issue type is in:

Permissions required:

  • For custom issue type avatars, Browse projects project permission for at least one project the issue type is used in.

The only ‘workaround’ is switching to using OAuth, then you can use read:avatar:jira scope and call the request using asApp()

We are trying to implement in a Connect app, making the request as app, and we get the 401 error. We have, for the app, the READ, ADMIN and ACT_AS_USER scopes configured, so getting this shouldn’t be an issue, right?

Any idea on other avenues I can explore?