[
https://issues.apache.org/jira/browse/CAMEL-22080?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17952561#comment-17952561
]
Mikael Andersson Wigander commented on CAMEL-22080:
---------------------------------------------------
One suggested solution could be to add one more argument where the user can
choose how the cache should behave:
{{OAuth2URIAndCredentials.of(requestUri, clientId, clientSecret,
cacheStrategy)}}
Where {{cacheStrategy}} could be one of:
* {{HOST_ONLY}} (default)
* {{HOST_AND_PATH}}
* {{FULL_URI}}
This would let users fine-tune their caching granularity.
> Http component oauth2 cache based on the full endpoint URI
> ----------------------------------------------------------
>
> Key: CAMEL-22080
> URL: https://issues.apache.org/jira/browse/CAMEL-22080
> Project: Camel
> Issue Type: Improvement
> Components: camel-http
> Reporter: Mikael Andersson Wigander
> Priority: Minor
>
> In the http component there's a setting to cache the token,
> .oauth2CacheTokens(true).
> This cache is using the complete URI including dynamic parts which makes it
> request a new token when the path changes.
> [https://localhost/event/1]
> [https://localhost/event/2]
> Both above are cached so a subsequent call to any of these will be using the
> cache but the initial call will call the oauth2TokenEndpoint URI for both of
> them and request a new token.
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
