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: set xpack.security.encryptionKey #1738

Closed
jordansissel opened this issue Sep 17, 2019 · 0 comments · Fixed by #2278
Closed

Kibana: set xpack.security.encryptionKey #1738

jordansissel opened this issue Sep 17, 2019 · 0 comments · Fixed by #2278
Assignees
Labels
>enhancement Enhancement of existing functionality

Comments

@jordansissel
Copy link
Contributor

jordansissel commented Sep 17, 2019

Per the docs:

By default, a value is automatically generated in memory. If you use that default behavior, all sessions are invalidated when Kibana restarts.

The unspoken note here is that with 2 or more instances, each Kibana will generate its own key. This causes all kibana instances to reject eachother's login cookies.

The user experience when this happens goes like this:

  • Visit kibana, receive login prompt.
  • Login correctly
  • Get redirected to whatever landing page is appropriate
  • Get a 403/redirected back to the login prompt because your 2nd request actually went to a different Kibana which rejected the previous Kibana instance's session cookie, insisting that you need to login.

To resolve this, set xpack.security.encryptionKey the same on all Kibana instances.

Recommend ECK sets this value for the Kibana resource.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
>enhancement Enhancement of existing functionality
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants