Issue does not exist or you do not have permission to see it.

[Maulik Panchal]

Hello,

I want to create an issue with REST API and followed https://developer.atlassian.com/server/jira/platform/jira-rest-api-example-create-issue-7897248/ this flow. 

Tried endpoint as : http://<projectname>.atlassian.net/rest/api/2/issue/ on postman with same request parameter . But not getting the response in positive. (tried with api/2 & api/3 both)

It shows "You do not have permission to create issues in this project." error message. with POST method. Tried with GET and it shows a 405 error code.

In additional , I reviewed and tried as per suggested on https://community.atlassian.com/t5/Jira-questions/Rest-API-Issue-does-not-exist-or-you-do-not-have-permission-to/qaq-p/1165586 but no difference.

[Ed Gaile _Atlanta_ GA_]

What authentication are you using in your API calls? If you are using basic authentication (username/password), you need to make sure the User exists in Jira and has the appropriate permissions for the target project (i.e browse, create issue, etc..)

[Maulik Panchal]

Yes, I tried with basic authentication (username/password) but it respond as "Basic authentication with passwords is deprecated. "

Attached SS: https://nimb.ws/LRTypt

In regard of permissions, can you share with me the Documentation URL or something that describes requiring permission in more details?

[Maulik Panchal]

I tried basic authentication with username: password (working credentials of the browser) but it looks deprecated. (https://developer.atlassian.com/cloud/confluence/deprecation-notice-basic-auth/)

So I tried with Bearer token and OAuth 2.0 both.

On the issue with authentication, it shows an error message. However, on working credentials it came back to the main error (Issue does not exist...).

[Nic Brough -Adaptavist-]

Then the account the credentials are for does not have permission to see the issue you are trying to work with.

[Maulik Panchal]

I have applied for all possible permissions on project and issue related points. I allowed access as public so no restriction applies.

FYI : I am using a free plan.  (Hope it does not affect permission scenarios )

[Nic Brough -Adaptavist-]

The use of permissions in the free plan is limited, you can't configure it to use the more clever things permissions can do.  But the limitations don't apply to the basic access you are looking at here.

It is very simple for this error message - either your credentials are incorrect, or the user you are logging in as does not have permission to create issues in that project.

[Maulik Panchal]

Yes, as per the response message, it's clear. But Basic Auth shows "Basic authentication with passwords is deprecated. " Attached SS: https://nimb.ws/LRTypt

What's the reason for this? And seeking its solution.

[Nic Brough -Adaptavist-]

The reason is that basic authentication is not as secure as it should be. 

So it's been deprecated, and you'll need to use tokens or oauth.