-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
[Filebeat][Inputs][HTTP JSON] Multi-Step/API Requests #31117
Comments
Some support for multi-step or chained httpjson calls was added in #29816. It is tagged for 8.3 but looks like it made the cutoff for the upcoming 8.2 release. I'm not sure it would support setting the Authorization header as in your example though, it likely needs to be extended further to allow that. |
Pinging @elastic/security-external-integrations (Team:Security-External Integrations) |
I have a work-in-progress that would be able to do this in #31233 (though not as part of HTTP JSON). If this goes in, it is likely to be in the new V2 input system. |
One use case example is JAMF Protect. https://docs.jamf.com/jamf-protect/documentation/Jamf_Protect_API.html |
@BenB196 Hey there, are you still looking for this feature to be implemented in httpjson or were you able to solve the issue you were facing ? |
@BenB196 any updates on this ? |
This is likely fully possible with the new CEL input. |
Closing this issue for the moment, since an alternative solution using CEL is available |
Describe the enhancement:
I'd like to request the ability to specify running multiple steps (API calls) in a single HTTP JSON input configuration.
Describe a specific use case for the enhancement or feature:
There are some APIs which require you to first authenticate against an
auth
endpoint, to get an API token, to then use to execute an API call. This requires 2 different URLs/APIs to be used in a single input.Example Flow
An example of this type of flow.
clientId
and asecret
, and you make a call like:curl -X POST -u "<clientId>:<secret>" my-api.com/auth
curl -X GET -H "Authorization: <accessToken>" my-api.com/realAPI
Reading through the docs, this doesn't seem possible currently.
The text was updated successfully, but these errors were encountered: