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

Kibana needs to display better error message when user with disabled role logs in #36129

Closed
bhavyarm opened this issue May 6, 2019 · 4 comments
Labels
enhancement New value added to drive a business result Team:Security Team focused on: Auth, Users, Roles, Spaces, Audit Logging, and more!

Comments

@bhavyarm
Copy link
Contributor

bhavyarm commented May 6, 2019

Kibana version: 7.1.0 BC1

Elasticsearch version: 7.1.0 BC1

Server OS version: darwin_x86_64

Browser version: chrome latest

Browser OS version: os x

Original install method (e.g. download page, yum, from source, etc.): from staging

Describe the bug: If user with a disabled role logs into Kibana - Kibana just displays {"statusCode":403,"error":"Forbidden","message":"Forbidden"}.

Also if another user needs to log in - user has to clear the cookies.

Steps to reproduce:

  1. On trial license create a role with fls and assign it to user
  2. login to Kibana with that user and everything is fine
  3. logout and login as elastic user and downgrade the license to basic - notice that role from step one is disabled
  4. logout and login with user from step 1
  5. Kibana displays {"statusCode":403,"error":"Forbidden","message":"Forbidden"} without giving any details about the error.

Disabled role:
Screen Shot 2019-05-06 at 1 44 38 PM

Screen Shot 2019-05-06 at 2 21 59 PM

@bhavyarm bhavyarm added bug Fixes for quality problems that affect the customer experience Team:Security Team focused on: Auth, Users, Roles, Spaces, Audit Logging, and more! labels May 6, 2019
@elasticmachine
Copy link
Contributor

Pinging @elastic/kibana-security

@kobelb
Copy link
Contributor

kobelb commented May 6, 2019

@bhavyarm this should be addressed as one of the causes for #18270

@jpcarey
Copy link

jpcarey commented May 9, 2019

huge +1 for fixing this.

@kobelb kobelb added enhancement New value added to drive a business result and removed bug Fixes for quality problems that affect the customer experience labels Jan 14, 2020
@legrego
Copy link
Member

legrego commented Feb 5, 2021

This was resolved by #75538, and is available in the 7.10.0 release 🎉

@legrego legrego closed this as completed Feb 5, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New value added to drive a business result Team:Security Team focused on: Auth, Users, Roles, Spaces, Audit Logging, and more!
Projects
None yet
Development

No branches or pull requests

5 participants