[
https://issues.apache.org/jira/browse/NIFI-9984?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anders updated NIFI-9984:
-------------------------
Labels: StandardOauth2AccessTokenProvider (was: )
> Support additional successful status codes in
> StandardOauth2AccessTokenProvider
> -------------------------------------------------------------------------------
>
> Key: NIFI-9984
> URL: https://issues.apache.org/jira/browse/NIFI-9984
> Project: Apache NiFi
> Issue Type: Improvement
> Affects Versions: 1.16.1
> Reporter: Anders
> Priority: Minor
> Labels: StandardOauth2AccessTokenProvider
>
> The StandardOauth2AccessTokenProvider controller service only supports
> reponse status code 200:
> https://github.com/apache/nifi/blob/5aa71570ff1781f83f9fb8bf16ed3ab386d06b85/nifi-nar-bundles/nifi-standard-services/nifi-oauth2-provider-bundle/nifi-oauth2-provider-service/src/main/java/org/apache/nifi/oauth2/StandardOauth2AccessTokenProvider.java#L322
> And while this adheres to the RFC
> (https://datatracker.ietf.org/doc/html/rfc6749#section-5.1), it is not
> uncommon to use 201.
> One example:
> https://www.ibm.com/docs/en/dbaoc?topic=applications-using-oauth-20-based-authentication
> It would be useful if the StandardOauth2AccessTokenProvider controller
> service at least allowed for 201 in addition to 200.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
