Roman created NIFI-13603:
----------------------------

             Summary: Support for other content-type in 
StandardOauth2AccessTokenProvider
                 Key: NIFI-13603
                 URL: https://issues.apache.org/jira/browse/NIFI-13603
             Project: Apache NiFi
          Issue Type: Improvement
            Reporter: Roman
         Attachments: screen1.png, screen2-added-content-type.jpg, 
screen_error2.jpg, screen_error3.png

As a Nifi developer I would like to use StandardOauth2AccessTokenProvider with 
content-type other then default one *application/x-www-form-urlencoded*

Right now it is not possible and there is no way to add additional header to 
StandardOauth2AccessTokenProvider. So just add Content-Type like in InvokeHttp 
processor


{code:java}
The request entity's media type 'application/x-www-form-urlencoded' is not 
supported {code}

Slack conversation:

https://apachenifi.slack.com/archives/C0L9VCD47/p1722419111289389



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to