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

Standardize Error Messages in Kibana Under Stack Management for Access Deny #83607

Closed
augustynd opened this issue Nov 18, 2020 · 4 comments
Closed
Labels
Team:Security Team focused on: Auth, Users, Roles, Spaces, Audit Logging, and more!

Comments

@augustynd
Copy link

This is related to Spaces in Kibana and permissions. Right now, under Stack Management, when a user doesn't have permissions to manage anything in Kibana, the user is still presented with all Kibana functions such as: Ingest, Data, Alerts and Insights, Security, Stack, Kibana, etc. and there are a bunch of random errors for the same issue - access denied - when the user clicks on any of the above.

The errors are not standardized, and they can confuse a user.

error-5
error-4
error-3
error-2
error-1

@flash1293
Copy link
Contributor

Which version are you running on? I'm seeing #67791 which in theory should handle this problem by simply hiding the menu items which can't be accessed right now. It should be part of the 7.10.0 release.

@flash1293 flash1293 added the Team:Security Team focused on: Auth, Users, Roles, Spaces, Audit Logging, and more! label Nov 18, 2020
@elasticmachine
Copy link
Contributor

Pinging @elastic/kibana-security (Team:Security)

@legrego
Copy link
Member

legrego commented Nov 18, 2020

I agree - this feels like a duplicate of #35796, which is resolved by #67791 in version 7.10.0

@augustynd
Copy link
Author

Ok, this seems to be already addressed, I'm on 7.9.1 still. Thank you.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Team:Security Team focused on: Auth, Users, Roles, Spaces, Audit Logging, and more!
Projects
None yet
Development

No branches or pull requests

4 participants