[Response Ops][Task Manager][PoC] Run tasks as the current user #205577
+277
−10
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Resolves: #190661
This PR is a proof of concept allowing tasks to be ran scoped as the current user. It accomplishes this by creating an API when the user schedules this task. It will then persist the API key in the task instance which allows the task handler to have access to the user's privileges.
To test:
yarn start --run-examples
http://localhost:5601/app/triggersActionsUiExample/task_manager_with_api_key
Schedule Task 1 and 2
, this will schedule a mock test that is defined inx-pack/platform/plugins/shared/alerting/server/plugin.ts
, which prints out the task instance and the scoped clients.Remove
to cancel the task, which then cleans up and invalidates the API keys.Remove All Tasks
which will bulk remove tasks and invalidate API keys.Limitation of this approach: