[
https://issues.apache.org/jira/browse/NIFI-15070?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18042063#comment-18042063
]
ASF subversion and git services commented on NIFI-15070:
--------------------------------------------------------
Commit a954d2cb317629086674f9a3ac0d7dfff0cffcc5 in nifi's branch
refs/heads/main from Peter Turcsanyi
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=a954d2cb31 ]
NIFI-15070 Fixed OAuth2AccessTokenProvider for Access Tokens without expiration
(#10401)
- Added Default Expiration Time to StandardOauth2AccessTokenProvider
Signed-off-by: David Handermann <[email protected]>
> OAuth2AccessTokenProvider should properly handle access tokens without
> expiration time
> --------------------------------------------------------------------------------------
>
> Key: NIFI-15070
> URL: https://issues.apache.org/jira/browse/NIFI-15070
> Project: Apache NiFi
> Issue Type: Bug
> Reporter: Peter Turcsanyi
> Assignee: Peter Turcsanyi
> Priority: Major
> Time Spent: 2.5h
> Remaining Estimate: 0h
>
> OAuth 2.0 access tokens typically have a finite (and in most cases short)
> expiration time which is set by the token provider. However, some providers
> (like Salesforce) issue permanent tokens that have no expires_in field. These
> tokens are handled incorrectly on NiFi side, because AccessToken.expiresIn is
> initialized with 0 and actually it means the opposite: the token gets expired
> immediately. This leads to requesting a new token every time which affects
> the performance and the client may also be banned due to the continuous token
> requests (e.g QuerySalesforceObject downloading a large dataset using
> pagination).
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
