[skip ci] Check point on token provider #25971
Closed
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
do not merge
I'm pushing this as a testable checkpoint for the new token provider implementation.
authorization
header contents in cookie when using basic auth headers d595fd2Kibana
You will need extra privileges on the internal server user. Either compile Elasticsearch with elastic/elasticsearch#35751 and use the built-in
kibana
user, or update kibana.yml with a new user that has thekibana_system
role plus a new role that grants access tocluster:admin/xpack/security/token/*
:Then add this to your kibana.yml:
Elasticsearch
If you're not using TLS in your dev install of Elasticsearch, you'll need to manually enable the token service (note, this won't work for production).
The default expiration for tokens is like 30 minutes or something, so you'll probably want to make that smaller while playing around with this if you want to verify the session renewal/refresh token logic: