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.

Sign up for GitHub

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

Jump to bottom

It isn't possible to assign different privileges to different actions when they are based off of the same connector #70084

Closed
gmmorris opened this issue Jun 26, 2020 · 4 comments
Closed

It isn't possible to assign different privileges to different actions when they are based off of the same connector #70084

gmmorris opened this issue Jun 26, 2020 · 4 comments
Labels
enhancement New value added to drive a business result estimate:needs-research Estimated as too large and requires research to break down into workable issues Feature:Actions/Framework Issues related to the Actions Framework Feature:Actions Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams)

Comments

@gmmorris
Copy link
Contributor

This is a step towards addressing #69442

RBAC for connectors/actions such that you can (perhaps) apply different privileges across these actions.
@gmmorris gmmorris mentioned this issue Jun 26, 2020
Open
4 tasks
@azasypkin azasypkin added Feature:Actions Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams) labels Jun 29, 2020
@elasticmachine
Copy link
Contributor

Pinging @elastic/kibana-alerting-services (Team:Alerting Services)

@gmmorris gmmorris mentioned this issue Mar 22, 2021
Open
@gmmorris gmmorris added the Feature:Actions/Framework Issues related to the Actions Framework label Jul 1, 2021
@gmmorris gmmorris added the loe:needs-research This issue requires some research before it can be worked on or estimated label Jul 14, 2021
@gmmorris gmmorris added enhancement New value added to drive a business result estimate:needs-research Estimated as too large and requires research to break down into workable issues labels Aug 13, 2021
@gmmorris gmmorris removed the loe:needs-research This issue requires some research before it can be worked on or estimated label Sep 2, 2021
@kobelb kobelb added the needs-team Issues missing a team label label Jan 31, 2022
@botelastic botelastic bot removed the needs-team Issues missing a team label label Jan 31, 2022
@mikecote
Copy link
Contributor

mikecote commented May 4, 2023

@cnasikas have you heard of such request (to have RBAC per sub-action)?

@cnasikas
Copy link
Member

cnasikas commented May 5, 2023

No, so far. I think it is ok if we close this and revise it in the future if needed.

@mikecote
Copy link
Contributor

mikecote commented May 5, 2023

Sounds good, thanks!

@mikecote mikecote closed this as completed May 5, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement New value added to drive a business result estimate:needs-research Estimated as too large and requires research to break down into workable issues Feature:Actions/Framework Issues related to the Actions Framework Feature:Actions Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams)
Projects
No open projects
AppEx: ResponseOps - Execution & Connectors
Status: Done
Milestone
No milestone
Development

No branches or pull requests
6 participants
@gmmorris @kobelb @azasypkin @mikecote @cnasikas @elasticmachine