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

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

Closed
bfgiordano opened this issue Sep 19, 2018 · 9 comments
Labels

Comments

@bfgiordano
Copy link

Session Info
@sckott
Copy link
Contributor

sckott commented Sep 19, 2018

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 es_user/es_pwd in connect() and those should are used in simple auth.

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)

@sckott
Copy link
Contributor

sckott commented Sep 26, 2018

@bfgiordano did you try setting es_user and es_pwd in connect()?

@bfgiordano
Copy link
Author

bfgiordano commented Sep 26, 2018 via email

sckott added a commit that referenced this issue Oct 4, 2018
#232 #87 more work on refining connection handler and moving fxns and egs to use connection object
  not done yete
@sckott sckott added this to the v1.0 milestone Mar 12, 2019
@sckott sckott modified the milestones: v1.0, v1.1 Apr 5, 2019
@sckott
Copy link
Contributor

sckott commented Dec 20, 2019

@bfgiordano sorry for long delay in responding here - In the current version of elastic, we should now be able to support certs, see ?connect and the examples - let me know if it works for you

@sckott sckott removed this from the v1.1 milestone Jan 10, 2020
@sckott sckott closed this as completed Jan 10, 2020
@peterpramb
Copy link

@sckott Unfortunately cainfo is currently not passed to crul as documented, it has to be set explicitly:

library("elastic")
library("crul")
set_opts(cainfo = "/path/to/ca.file")
x = connect()
x$info(verbose = TRUE)
packageVersion("elastic")
[1] ‘1.1.0’
packageVersion("crul")
[1] ‘0.9.0’

@peterpramb
Copy link

Hm, rather strange:

connect(..., cainfo = "/path/to/ca.file")$info(verbose = TRUE) does not work without set_opts, but Search() does...

@sckott
Copy link
Contributor

sckott commented Feb 11, 2020

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?

@peterpramb
Copy link

@sckott I don't have the exact error message at hand, but the verbose info output shows curl using the system's default CA store instead of the provided one.

@sckott
Copy link
Contributor

sckott commented Feb 18, 2020

thanks - will have a look soon

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants