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.

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] Check boxes are displayed under rules page for read Security privilege #126314

Closed
ghost opened this issue Feb 24, 2022 · 4 comments
Assignees
Labels
bug Fixes for quality problems that affect the customer experience fixed impact:medium Addressing this issue will have a medium level of impact on the quality/strength of our product. QA:Validated Issue has been validated by QA Team:Detections and Resp Security Detection Response Team Team:Security Solution Platform Security Solution Platform Team Team: SecuritySolution Security Solutions Team working on SIEM, Endpoint, Timeline, Resolver, etc. v8.1.1 v8.2.0

Comments

@ghost
Copy link

ghost commented Feb 24, 2022

Describe the bug
Check boxes are displayed under rules page for read Security privilege

Build Details:

Version: 8.1.0 BC3
Commit:0335dd6a26ef29ae9021d0fae9347dc88f3b7d6e
Build:50346 

Preconditions

  1. N/A

Steps to Reproduce

  1. Navigate to Stack Management > Role
  2. Create a Role with below configuration
    image

image

  1. Assign above role to a user and login with same
  2. Navigate to Rules page
  3. Observe that Check boxes are displayed under rules page for read Security privilege

Actual Result
Check boxes are displayed under rules page for read Security privilege

Expected Result
Check boxes should not be displayed under rules page for read Security privilege, like Cases page:

image

What's Working

  • N/A

What's Not Working

  • N/A

Screen-Shot
image

@ghost ghost added bug Fixes for quality problems that affect the customer experience triage_needed Team: SecuritySolution Security Solutions Team working on SIEM, Endpoint, Timeline, Resolver, etc. labels Feb 24, 2022
@elasticmachine
Copy link
Contributor

Pinging @elastic/security-solution (Team: SecuritySolution)

@ghost ghost added v8.1.0 impact:medium Addressing this issue will have a medium level of impact on the quality/strength of our product. labels Feb 24, 2022
@ghost ghost assigned ghost and MadameSheema and unassigned ghost Feb 24, 2022
@MadameSheema MadameSheema added Team:Detections and Resp Security Detection Response Team Team:Security Solution Platform Security Solution Platform Team labels Feb 28, 2022
@elasticmachine
Copy link
Contributor

Pinging @elastic/security-detections-response (Team:Detections and Resp)

@yctercero
Copy link
Contributor

Ready for QA check!

kibanamachine added a commit that referenced this issue Mar 8, 2022
#126827) (#127097)

Resolves #126328 and #126314.

(cherry picked from commit 18a5344)

Co-authored-by: Yara Tercero <yctercero@users.noreply.github.com>
@ghost
Copy link
Author

ghost commented Mar 14, 2022

Hi @MadameSheema

We have validated this issue on 8.2.0 SNAPSHOT and Observed that issue is Fixed 🟢

Please find below the testing details:

Build Details:

Version: 8.2.0 SNAPSHOT
Commit: e1578ee2b5b4dfbab59113a9c58854799f4f7b42
Build: 51037

Screenshot:

check boxes

Hence, We are closing this issue and marking as QA Validated

Thanks !!

@ghost ghost closed this as completed Mar 14, 2022
@ghost ghost added the QA:Validated Issue has been validated by QA label Mar 14, 2022
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Fixes for quality problems that affect the customer experience fixed impact:medium Addressing this issue will have a medium level of impact on the quality/strength of our product. QA:Validated Issue has been validated by QA Team:Detections and Resp Security Detection Response Team Team:Security Solution Platform Security Solution Platform Team Team: SecuritySolution Security Solutions Team working on SIEM, Endpoint, Timeline, Resolver, etc. v8.1.1 v8.2.0
Projects
None yet
Development

No branches or pull requests

3 participants