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

Enable native realm in addition to the file realm #2037

Closed
charith-elastic opened this issue Oct 22, 2019 · 3 comments · Fixed by #2038
Closed

Enable native realm in addition to the file realm #2037

charith-elastic opened this issue Oct 22, 2019 · 3 comments · Fixed by #2038
Assignees
Labels
>bug Something isn't working v1.0.0

Comments

@charith-elastic
Copy link
Contributor

It seems that the native realm is only enabled by default if no other realms have been defined. In #1698 we explicitly enabled the file realm -- which results in the native realm getting disabled and preventing users from authenticating using the credentials they create using the UI. See #2036.

@eedugon
Copy link
Contributor

eedugon commented Oct 23, 2019

For reference purposes, there's a valid workaround explained here:
https://discuss.elastic.co/t/new-user-cant-login-kibana/204810/2

It consists of explicitly enabling the native realm.

@ransoor2
Copy link

I did the workaround. Now I'm able to log in, but I get "Error in visualization [esaggs] > Internal Server Error" when trying to access Kibana dashboards.
Elastic version 7.4.2
elastic

@sebgl
Copy link
Contributor

sebgl commented Nov 21, 2019

@ransoor2 this looks unrelated to the native realm issue. Please check both Kibana and Elasticsearch logs and create a new issue or discuss topic where appropriate.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
>bug Something isn't working v1.0.0
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants