You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The content you are editing has changed. Please copy your edits and refresh the page.
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).
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
The text was updated successfully, but these errors were encountered: