The Atlassian Community Forums are currently in read-only mode. We will be relaunching on a new platform on September 22 (read more here). We apologize for the extended downtime. For concerns or questions, please email communitymanagers@atlassian.com. See you on the other side, on the new Atlassian Community Forums! :)
Atlassian Team members are employees working across the company in a wide variety of roles.
November 9, 2016 edited
If this only happens when the REST API call is authenticated with unlicensed JSD customer then this is a known issue: https://jira.atlassian.com/browse/JSD-1640. A fix is currently in development.
Edit:
My answer above is slightly misleading. Unlicensed (aka external) JSD customers are free, hence we have to restrict what paths are available. At the moment we've decided free customer should not be able to use JIRA REST API (even those available to anonymous), because we're restricting by the path prefix /rest/api/2/...
For this scenario, you can work around it by not authenticating the REST call with any user.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.