Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support oauth2 token caching #780

Open
1 task
sbuettner opened this issue Jun 26, 2023 · 1 comment
Open
1 task

Support oauth2 token caching #780

sbuettner opened this issue Jun 26, 2023 · 1 comment
Labels
kind:enhancement New feature or request target:8.4

Comments

@sbuettner
Copy link
Contributor

Is your feature request related to a problem? Please describe.

As discussed in this forum thread the http outbound connector is issuing a new token for every request. This can lead to a high amount of token issue request on the customer side which can be prevented by caching the generated token for a configured amount of time.

Describe the solution you'd like

The http outbound connector should support caching of token to re-use previously issued tokens when creating outbound requests.

Tasks

Preview Give feedback
@sbuettner sbuettner added the kind:enhancement New feature or request label Jun 26, 2023
@geemov42
Copy link

Hello,
I understand the problematic but I see the things in an alternative way that let us do what we want concerning the http request security.
When we look, rest and soap are based on http but need different kind of security. To do the job I have modified some class to support the security delegation to an external component like spring security.
With this modification I can let spring security manage the tokens (because you could have multiple client registration).

You can find the intellij path in attachment :
add_the_possibility_to_use_an_external_component_to_secure_a_request.patch

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind:enhancement New feature or request target:8.4
Projects
None yet
Development

No branches or pull requests

2 participants