Jira Issue Collector embedded in website not loading for all users - 403 error

[Robert Shattock]

We have a Jira Issue Collector on our website - it correctly loads for some users (see below) and when in incognito mode  

- for other users it used to load until several weeks ago and has now stopped working.

The call to https://xxxx.atlassian.net/rest/collectors/1.0/configuration/trigger/4e515c20?os_authType=none&callback=trigger_4e515c20 comes back with a 403 status code

<status>

<status-code>403</status-code>

<message>The user does not have the correct application access required for this resource</message>

</status>

My best guess is that it's a Jira permissions thing... you don't need to be logged into Jira to use the Jira Issue Collector BUT I suspect if you are logged in it tries to do something (highlighted by the fact that it seems to work for those of us with Jira access with our Atlassian accounts and when in incognito). The users being denied would have Atlassian accounts for Confluence.  I'm not aware of anything at our end having changed recently re: users and Atlassian billing/licensing - has Atlassian changed anything recently?

[Robert Shattock · Accepted solution]

This issue has resolved itself without any changes at our end.

Given what I'd seen I'd say the issue was at the Atlassian end of things and was probably silently fixed after they saw an influx of errors.

Challenge of software as a service.