-
Notifications
You must be signed in to change notification settings - Fork 58
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
Does connect() support providing SSL certs, as well as username/password for HTTPS? For Xpack Security (paid features) - ES v5.5, v6.2, 6.3, 6.4 #232
Comments
thanks for your question @bfgiordano SSL certs aren't supported at the moment, but I do have a branch here (see #87) where I'm re-working the how the connection is done and can include this. I already have username/pwd support, see parameters I don't have any explicit support for xpack because i don't have a paid install and Elasticsearch won't give me access to xpack, so ther's no way to test it (so not worth supporting) |
@bfgiordano did you try setting |
Yes we did but we are using SSL and need to also pass certs which your package does not appear to support directly. We tried setting cainfo to the path to the cert file (.pem) and then doing a connect with username/password but that did not work - no error reported on the connect, but also no data returned from the ES cluster on search request.
…Sent from my iPhone
On Sep 26, 2018, at 12:30 PM, Scott Chamberlain ***@***.***> wrote:
@bfgiordano did you try setting es_user and es_pwd in connect()?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.
|
@bfgiordano sorry for long delay in responding here - In the current version of |
@sckott Unfortunately
|
Hm, rather strange:
|
thanks @peterpramb interesting, i'll have a look and see why its working in some cases but not others. when it doesn't work I assume you're getting an unauthorized error? |
@sckott I don't have the exact error message at hand, but the verbose |
thanks - will have a look soon |
Session Info
The text was updated successfully, but these errors were encountered: