[
https://issues.apache.org/jira/browse/NIFI-15070?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Peter Turcsanyi updated NIFI-15070:
-----------------------------------
Status: Patch Available (was: Open)
> 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: 10m
> 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)
