Hello folks!We are trying to get options for custom field as described here:https://developer.atlassian.com/cloud/jira/platform/rest/v3/?utm_source=%2Fcloud%2Fjira%2Fplatform%2Frest%2F&utm_medium=302#api-rest-api-3-customField-fieldId-option-getbut seems like this works with login\password credentials only and for OAuth flow it says "OAuth 2.0 is not enabled for this method."
Are there any plans to support OAuth 2.0 for this particular endpoint? Such a limitation is quite disappointing ...
Would appreciate any suggestions \ workarounds
Hello @Volodymyr OSTAPIV ,
Welcome to the Atlassian community!
If I understand correctly, you are able to call the Get options for field REST API endpoint (GET /rest/api/3/customField/{fieldId}/option) using Basic Authentication with email address and API Token, but this is not working when using Oauth 2.
This looks similar to what is discussed in the below thread:
In there the issue was caused by the bug tracked as: [JRACLOUD-72126] Using Latest API reports OAuth is not enabled
Can you kindly check if this is the same issue?
In case it is not, please call the REST API endpoint again using Curl making sure to include the -D- flag to print the whole header and paste the response in your reply, making sure to remove/hide the sensitive data (e.g. token, instance name, etc.) .
Cheers,Dario
Hi!I'd like to let you know that I have enabled
/customField/{fieldId}/option
endpoints for OAuth and now you can use it in 3LO apps.
Do not hesitate to reach us when you are facing any other issues.Enjoy!
Hi Dario!
Here https://jira.atlassian.com/browse/JRACLOUD-72126 people are able to hit `V3` endpoint and issue appears for the `latest` only.
In my case it doesn't work for V3 either (when using OAuth 2.0), but the same mechanism allows to access almost all the endpoints. I think its a Jira API limitation because all the doc pages but this have OAuth scopes required mentioned.
I will try to figure out request details follow up. But could you please check maybe its documented limitation.
Regards, Volodymyr
Here are request details:
HttpRequest{method=GET, uri=https://api.atlassian.com/ex/jira/91d237d6-0c68-47c8-a8f6-885f45dfc126/rest/api/3/customField/10036/options, headers=[Pair{Authorization=Bearer ey#REDACTED#mg}, Pair{ATL-TraceId=1364dd31-19a5-4530-85be-547c914ca5f0}], body=null}
Nothing special...
Headers from curl:
HTTP/2 403 vary: Accept-Encoding,Accept-Encodingcontent-type: application/json;charset=UTF-8strict-transport-security: max-age=315360000; includeSubDomains; preloaddate: Sat, 11 Apr 2020 06:21:06 GMTx-request-id: c60dabe49804393fx-arequestid: 816a81bb-5842-4a19-b00a-282a665e39f9x-application-context: Stargate:prod,prod-euwest:8080x-xss-protection: 1; mode=blocktiming-allow-origin: *x-content-type-options: nosniffmicros-issuer: micros/edge-authenticatorx-frame-options: SameOriginexpect-ct: report-uri="https://web-security-reports.services.atlassian.com/expect-ct-report/global-proxy", enforce, max-age=86400
Response:
{"errorMessages":["OAuth 2.0 is not enabled for this method."]}
It looks like you're new here. Sign in or register to get started.