[NIFI-9984] Support additional successful status codes in StandardOauth2AccessTokenProvider

• Type: Improvement
• Status: Resolved
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 1.16.1
• Fix Version/s: 1.17.0, 1.16.2
• Labels: StandardOauth2AccessTokenProvider
• Assignee: David Handermann
• Reporter: Anders
• Created: 04/May/22 09:16
• Updated: 09/May/22 17:58
• Resolved: 04/May/22 21:32

Description

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.

Issue Links

• links to: GitHub Pull Request #6016