You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Enable search sessions in the Kibana settings yml: xpack.data_enhanced.search.sessions.enabled: true
Create a spaces role without stack management privileges, e.g. only read access to Discover in the Default space:
Create a user and assign the before created role only
Log in with that user
Expected result
The user doesn't see the Stack Management menu entry.
Actual result
The user sees the Stack Management menu entry, which contains the Kibana / Search Sessions entry.
Additional information
This makes UI feature_controls tests on cloud fail, because the above mentioned setting is active there for API and UI tests. In CI tests the setting is only used for API tests, so the menu entry is never shown during UI tests and feature controls tests are passing fine.
We probably need privileges to control the presence of this menu entry.
Do we still need the feature flag in the Kibana settings to enabled/disable this menu entry? If so, we might want to enable it for UI tests as well to make sure everything is working ok? Ideally, we would have some UI tests for it as well.
Found in version
Browser
Steps to reproduce
xpack.data_enhanced.search.sessions.enabled: trueDefaultspace:Expected result
Stack Managementmenu entry.Actual result
Stack Managementmenu entry, which contains theKibana / Search Sessionsentry.Additional information
feature_controlstests on cloud fail, because the above mentioned setting is active there for API and UI tests. In CI tests the setting is only used for API tests, so the menu entry is never shown during UI tests and feature controls tests are passing fine.