nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

The required parameter 'grant_type' is missing when requesting access token using OAuth 2.0

Jamshaid

I am trying to send a POST request to get the access_token using the following pattern of URL taken from here. It mentions that it will return an access token

curl -X POST https://atlassian.example.com/rest/oauth2/latest/token?client_id=CLIENT_ID&client_secret=CLIENT_SECRET&code=CODE&grant_type=authorization_code&redirect_uri=REDIRECT_URI&code_verifier=CODE_VERIFIER

but after passing the required parameters, it always says:

{

"error": "invalid_request",

"error_description": "The required parameter 'grant_type' is missing"

}

What am I missing? I have thoroughly checked each parameter but nothing is missing. It always say the same.

Accepted answers

Sebastian Brack

Hello @Jamshaid ,

just in case the problem is still relevant:

Maybe you forgot to set the Content-Type header in your POST request?

Content-Type: application/x-www-form-urlencoded

In my experience setting this header is necessary, otherwise the server seemingly doesn't even attempt to read the query parameters and just responds with the error you described.

All comments

Mayur Jadhav_30osel

Hello @Jamshaid ,

I hope you are doing well.

I hope you are following the correct steps.

Log in as a user with the JIRA System Administrators global permission.
Navigate to Administration > System > OAuth 2.0
Click on Add new integration
At the "Service provider", select Microsoft
Click on Copy at the Redirect URL field
Let's login to "https://portal.azure.com/"
Click on App registrations
Click on New registration
Let's pickup a friendly name so it will be easier to identify
Under the "Supported account types" section, let's choose "Accounts in any organizational directory (Any Azure AD directory - Multitenant) and personal Microsoft accounts (e.g. Skype, Xbox)"
Under the "Redirect URI" section, let's pickup Web and insert the URL from step #5 above
Click on Register
Click on API permissions
Click on Add a permission
Click on Microsoft Graph
Select Delegated permissions
Let's select the following permissions: OpenId permissions: offline_access IMAP: IMAP.AccessAsUser.All POP: POP.AccessAsUser.All
Click on Add permissions
Click on Grant admin consent for ...
Click on Certificates & secrets
Click on New client secret
Choose a description and expiration date
Take note of the Value generated (this will be used as the "Client secret" at Jira)
Click on Overview
Take note of the Application (client) ID (this will be used as the "Client ID" at Jira)
Let's go back to Jira and complete the configuration by inserting the following details:
Client ID (from step #25 above)
Client secret (from step #23 above)
Scopes: "https://outlook.office.com/IMAP.AccessAsUser.All", "https://outlook.office.com/POP.AccessAsUser.All" and "offline_access"
Click on Save
Test the connection
 If the connection was successful, please proceed
Navigate to Administration > System > Incoming Mail
Click on Add mail server
At the "Service Provider" field, let's pick up Microsoft Exchange Online / Outlook (IMAP)
At the "Username" field, insert the email address being used by Jira
At the "Authentication method" field, select the new server created under the OAuth 2.0 menu
Click on Authorize
Click on Test Connection
Click on Save

Regards,
Mayur

Jamshaid

I am using my own app to integrate it with Jira. I can access the following window and it returns the code successfully. But, when I make the 2nd request, it throws the above error

Sebastian Brack

Hello @Jamshaid ,

just in case the problem is still relevant:

Maybe you forgot to set the Content-Type header in your POST request?

Content-Type: application/x-www-form-urlencoded

In my experience setting this header is necessary, otherwise the server seemingly doesn't even attempt to read the query parameters and just responds with the error you described.

Jamshaid

Thanks a lot. It worked perfectly fine. Do I need to keep this header in further requests as well?

Jamshaid

this header is not mentioned anywhere in the docs.

Sebastian Brack

It should only be nessecary with POST requests. i.e requesting an access-token or refreshing your token. Everything you do with a GET request should work without it.

To make sure you can check in the REST API browser of your application.

e.g. In the Jira REST API Browser the token endpoints looks like this:

jira rest api browser.png

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

cloud

jira-software

jira-software-cloud

atl-gruland