-
Notifications
You must be signed in to change notification settings - Fork 8.2k
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
Make the /app/kibana#/management slug unique #33351
Comments
This sounds like a use case that would potentially be addressed already in x-pack security with RBAC (#18473), specifically Phase 3 Feature Controls (#20277). Either way, the plan is to make management its own app as we migrate to the new kibana platform (#31968) over the course of |
Ah, I missed this part when suggesting the use of RBAC & Feature Controls. If users don't have x-pack, then the URL situation should be sorted in the migration to the new platform as mentioned above. |
Closing as this has been resolved. |
Describe the feature:
In Kibana 7, when accessing the Kibana management interface it follows the URL pattern of
/app/kibana#/management
. This shares a similar root of/app/kibana
with discovery, visualize, dashboards, and possibly other tabs. Due to the use of the has, it makes restricting this URL very tedious / difficult (ex. ALBs will not allow you to create a rule for it).The feature I am requesting is to change the management section slug to a root of
/app/management
, similar to other sections (ex./app/apm
,/app/uptime
).Describe a specific use case for the feature:
If you don't have XPack, you want to be able to restrict the ability for everyone to make (potentially destructive) changes to the Kibana instance and underlying ES instances. It's currently very difficult to achieve this. I actually have not found a way to do this outside of the browser. Moving the
management
portion of the slug before the hashtag allows us to manage the behavior a bit better and restrict access to that portion of the interface.The text was updated successfully, but these errors were encountered: