Issue Summary

All the Curl examples on the Jira Service Management Cloud REST API page are wrong. They use bearer authentication instead of basic authentication with email address and API Token:

--header 'Authorization: Bearer <access_token>' \

 
instead of:

 --user 'email@example.com:<api_token>' \

 This is due to the fact that the Authentication for REST API requests section of the doc is still suggesting to use Oauth 1.0 that has been deprecated long time ago!

 If you are integrating directly with the Jira Service Management Cloud REST APIs it is recommended to use OAuth authentication method.

Steps to Reproduce

1. Open the Authentication for REST API requests section of the doc
2. See that it says  that it is recommended to use OAuth authentication method
3. Click on the link: "OAuth authentication" link

Expected Results

The Oauth method is indeed recommended 

Actual Results

At the top of the page it is clearly written that OAuth 1.0a is a legacy authentication method and, therefore, isn't recommended.

OAuth 1.0a is a legacy authentication method and, therefore, isn't recommended. Instead, check out the following for details of the recommended authentication approaches for:

• Connect apps, see Security for Connect apps.
• Connect apps that act on behalf of the user, see User impersonation for Connect apps.
• Non-Connect apps created in the developer console, see OAuth 2.0 (3LO) apps.
• Simple scripts or to make REST API calls yourself, see Basic auth for REST APIs.

See Integrating with Jira Service Management Cloud for more information on the options for developing with Jira Service Management Cloud.

Workaround

Use the Basic authentication method with an Atlassian account email address and API token