search

elastic / kibana

Your window into the Elastic Stack
https://www.elastic.co/products/kibana
Other
19.35k stars 7.98k forks source link

[Fleet]: Fleet tab is not accessible on All/Read privileges and integrations set to None/Read. #182638

Closed harshitgupta-qasource closed 1 week ago

harshitgupta-qasource commented 1 week ago

Kibana Build details:

VERSION: 8.14.0 BC3
BUILD: 73762
COMMIT: 2a492e1625f24336f3259b2b8df62b2b18127e81

Preconditions:

  1. 8.14.0-BC3 Kibana cloud environment should be available.

Steps to reproduce:

  1. Go to stack management -> Roles and click on “Create role”.
  2. In the “Kibana privileges” flyout, select: *Spaces: “All spaces”**.
  3. Under management section: Fleet: Select “Read”, Integrations: 'Read'.
  4. Click “Create global privilege”.
  5. Navigate to Stack Management -> Users .
  6. Click on “Create User” and Enter username, Password and choose one of the previously created roles, then click on “Create User”.
  7. Login with newly created User.
  8. Observe that Fleet tab is not accessible on All/Read privileges and integrations set to None/Read.

Note : Read privilege for Fleet is not available on 8.13.3 .

Expected Result: Fleet tab should accessible on All/Read privileges and integrations set to None/Read.

Screen Shot:

image

elasticmachine commented 1 week ago

Pinging @elastic/fleet (Team:Fleet)

harshitgupta-qasource commented 1 week ago

@amolnater-qasource Kindly review

amolnater-qasource commented 1 week ago

Secondary Review for this ticket is Done.

jen-huang commented 1 week ago

@harshitgupta-qasource @amolnater-qasource This case is only expected to work with subfeaturePrivileges experimental feature enabled. You should have the instructions to enable this on Cloud (since we have gotten good bug reports for this work 😉).

harshitgupta-qasource commented 1 week ago

Hi @jen-huang

Thank you for the confirmation. We just reported this issue to confirm if this feature will work like this for 8.14.0 release without the feature flag. Thanks!