-
-
Notifications
You must be signed in to change notification settings - Fork 296
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
Missing authentication header when requesting secured elassandra #273
Comments
Used sentinl version = v5.5.1 (https://github.com/sirensolutions/sentinl/releases/download/tag-5.5/sentinl-v5.5.1.zip) |
Same error with sentinl version 5.5.0 for kibana 5.5.0 as shown in the following trace
|
Hi @vroyer I need to confirm this with @sergibondarenko but I think this feature set is only available in 5.6.x we'll discuss backporting it as this is not the first request. Will update. |
Hi @vroyer
|
Hi Sergii,
This is a standard HTTP Basic authentication.
… Le 14 déc. 2017 à 12:26, Sergii Bondarenko ***@***.***> a écrit :
Hi @vroyer <https://github.com/vroyer>
What type of authentication is used?
When authentication is enabled on elassandra ...
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub <#273 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AJzHmWZGYta0mwLx9kf4rPbvVYZwb1rsks5tAQXPgaJpZM4RA1At>.
|
I've a similar error. I'm using kibana 5.6.5 basic authentication + sentinl 5.6.5 (tag 5.6.2) I've to change the authentication type of kibana? Thanks! |
I have the same issue with kibana 6.2.3, as describe in kibana issue #9583 It's definitly up to kibana to send the authorization header properly.... |
Concerning this feature, why don’t you use “elasticsearch.username” and “elasticsearch.password” in kibana.yml ? Globally, it would be great that all options in kibana.yml allowing to customize elasticsearch queries, are useable in sentinl. |
I believe if and when those are provided, the ES client in Kibana automatically resolves authentication for SENTINL as well @fbaligand did you have experience with the opposite condition? |
Happy to see it is the expected behavior, and so, that Sentinl use the official elasticsearch Kibana client (with all expected features). I will make a test to check all works as expected and will give you feedback. |
Well, kibana use its own account "kibana" to manage its configuration stored in elasticsearch, in index .kibana by default. For authenticated users, kibana act as a proxy and forward user's credential to elasticsearch, in order to check that the user have access to the requested index. Elassandra just check that all elasticsearch requests have a user credential (an Authorization header) matching a cassandra user with appropriate authorizations (for exemple having the SELECT permission to get/search in the index). Of course, if no credential is sent, access is refused according to the security policy. Hope this help. |
@lmangani |
Fix readme, v5.4.0
Issue Description
When authentication is enabled on elassandra (5.5.0.8 Help Regarding Output Syntax #146-branch), sentinl does not send any authentication header in one search request, and rejection cause an error. It should at least retry with the appropriate authentication header rather than throws an error. All other requests to elasticsearch are authenticated with the kibana account or the one used to log in kibana, here a watcher account.
Reproducing the Issue step-by-step
I can provide the elassandra enterprise code, license and conf to reproduce it if necessary.
Expected Results vs. Actual Results
Wireshark clear text trace of the sentinl request and response:
Elassandra audit trail
Elassandra error trace
Kibana error trace
The text was updated successfully, but these errors were encountered: