-
Notifications
You must be signed in to change notification settings - Fork 8.2k
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
[Security Solution][Endpoint] Update the run_endpoint_agent
dev script to support use of an API Key
#190449
[Security Solution][Endpoint] Update the run_endpoint_agent
dev script to support use of an API Key
#190449
Conversation
Pinging @elastic/security-defend-workflows (Team:Defend Workflows) |
@@ -62,6 +65,8 @@ export const cli = () => { | |||
--username Optional. User name to be used for auth against elasticsearch and | |||
kibana (Default: elastic). | |||
--password Optional. Password associated with the username (Default: changeme) | |||
--apiKey Optional. A Kibana API key to use for authz. When defined, 'username' |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Q: I don't see code change that ignores username/password, or is it already baked in?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@ashokaditya - yes, its backed into KbnClientExtended
class above. When api key is defined, we remove the creds from the URL and also intercept the .request()
calls and inject the API key header
💛 Build succeeded, but was flaky
Failed CI StepsMetrics [docs]
History
To update your PR or re-run it, just comment with: |
Summary
/x-pack/plugins/security_solution/scripts/endpoint/run_endpoint_agent.js
with a new optional argument:--apiKey
--username
and--password
username/password
is not ideal