[Security Solution]Duplicate warning pop-up are shown on attaching existing case to timeline when user have none access privilege to case.

[ghost]

Describe the bug
Duplicate warning pop-up are shown on attaching existing case to timeline when user have none access privilege to case.

Build Details:

Version: 7.14.0-SNAPSHOT
commit: 9838db392e7fcfc12f004b68fb1b09739f131148
Build Hash:41559
Artifact : https://artifacts-api.elastic.co/v1/search/7.14.0-SNAPSHOT

Browser Details:
N/A

Browser Details
All

Preconditions

1. Kibana user should be logged in.
2. Create a new user and assign below role to it.
3. Create a Role with All application to All and Case to None .
4. Case should be exist on above kibana environment. (creat with help of superuser)

Steps to Reproduce
1.login with user having read case privilege
2.Go to Timeline tab
3.Click on any timeline.
4.Click on Attach case > Existing case.
5.Observed that duplicate warning pop-up shown up , all having the same information.

Actual Result
Duplicate warning pop-up are shown on attaching existing case to timeline when user have none access privilege to case.

Expected Result
Single warning pop-up should show up on timeline on attaching existing case to timeline when user have none access privilege to case.

Whats Working

• N/A

Whats Not Working

• N/A

Screen-Shoot

logs
N/A

[elasticmachine]

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

[manishgupta-qasource]

Reviewed & Assigned to @MadameSheema

[elasticmachine]

Pinging @elastic/security-threat-hunting (Team:Threat Hunting)

[MadameSheema]

Thanks @karanbirsingh-qasource , I think this is the expected behaviour since we are getting an error per each one of the calls performed.

@cnasikas @jonathan-buttner can you please confirm?

[jonathan-buttner]

This is expected behavior, and as soon as this PR is merged: #101325

Readonly users will not see a button to attach cases from timeline. @manishgupta-qasource once my PR is merged can you confirm that this issue is resolved?

[jonathan-buttner]

Oops I mean @karanbirsingh-qasource could you confirm that it's resolved after my PR is merged.

[ghost]

sure @jonathan-buttner we we kill track of PR merge and regress the issue.

[cnasikas]

@karanbirsingh-qasource It should be fixed 🙂

[ghost]

Yes @cnasikas thank for the update now, user having None Access to Case sub-feature have no access to cases at all .

Hence closing this issue and adding "QA:Validated" to it.

thanks !!