-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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
Authentication to Kibana using API Keys #56087
Comments
Pinging @elastic/kibana-security (Team:Security) |
/cc @azasypkin potentially related to #53910 |
@kobelb do you know if it's acceptable to explicitly enable this functionality via Just a very rough idea I'm writing PoC for right now is that we may have xpack.security.authc.http:
enabled: true
autoSchemesEnabled: true
schemes: [ApiKey]
|
If it's possible to avoid needing to set a I like the direction you're going with the PoC, and I think it'd work perfectly for all other scenarios. Do you think it's possible for us to accept the |
Assuming you mean
It depends on how we frame it, if we have a good way to distinguish all necessary Fleet routes and whether we want to allow users to configure/disable this behavior or not. |
Yes we want fleet to be as easy to use as possible, so if we can avoid to have extra step to configure api key authorization it would be better |
FWIW, in my previous comment I forgot that API Keys work with |
Summary: Authentication via # default is xpack.security.authc.http.schemes: [apikey]
xpack.security.authc.http.schemes: [] |
Fleet will be using API Keys to authenticate to Kibana. They will potentially be doing so when only the basic auth provider is enabled in Kibana. They'll need a way to authenticate themselves in these scenarios.
The text was updated successfully, but these errors were encountered: