Skip to content
This repository has been archived by the owner on Aug 2, 2022. It is now read-only.

Security permission validation use cases #369

Open
ylwu-amzn opened this issue Jan 23, 2021 · 3 comments
Open

Security permission validation use cases #369

ylwu-amzn opened this issue Jan 23, 2021 · 3 comments
Labels
enhancement New feature or request

Comments

@ylwu-amzn
Copy link
Contributor

If user has no read permission of data source index, we should throw exception and block creating detector.
@ylwu-amzn ylwu-amzn added the enhancement New feature or request label Jan 23, 2021
@ylwu-amzn
Copy link
Contributor Author

And we should not show create alert button if user doesn't have create monitor permission, or disable the button.

@yizheliu-amazon
Copy link
Contributor

If user has no read permission of data source index, we should throw exception and block creating detector.

Is there any way to check if user has such permission or not?

@yizheliu-amazon
Copy link
Contributor

And we should not show create alert button if user doesn't have create monitor permission, or disable the button.

I guess this is worth another issue, or we change the title of this issue to Security permission validation use cases

@ylwu-amzn ylwu-amzn changed the title Check if user has read permission of data source index when create detector Security permission validation use cases Feb 5, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@ylwu-amzn @yizheliu-amazon