-
Notifications
You must be signed in to change notification settings - Fork 77
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
SSL/TLS Support? #50
Comments
Any updates regarding this? Thanks in advance |
Hi, I have same issue. The problem is located in logstash-output-mongodb.gemspec:
mongo ruby gem version 2.0.6 is too old and does not support ssl and tls options (only ssl=boolean). You need at least 2.4 or greater. Last version (2.8.0) has almost ssl/tls options. For example: https://jira.mongodb.org/browse/RUBY-1608 This is support for tls verifications in 2.7.0 |
HI, look this PR: |
Hi, I was able to execute logstash with latest ruby driver 2.7.2 against AWS documentdb using "?ssl=true&tlsInsecure=true" options. Use #52 for it. |
Hi @YakobovLior , The ssl issue is solved with latest ruby driver version for mongodb, and it allows to me to connect to docdb (mongodb version 3.6.0). In particular I use "ssl=true&tlsInsecure=true". I've used PR #52 and applied it to master, modified file
In particular, I use docker version, Dockerfile:
then:
and
With a pipeline like follows:
That's all |
I try to get i working with ssl but fail.
Without ssl (works if mongodb server is set to "allowSSL", what means that the output do not use ssl!):
output {
if [type] == "mytype" {
mongodb {
uri => "mongodb://myserver/"
database => "mydatabase"
collection => "mycollection"
id => "myid"
}
}
}
What i tried....
With ssl (mongodb server is set to "requireSSL", what means no ssl no data....):
output {
if [type] == "mytype" {
mongodb {
uri => "mongodb://myserver/mydatabase?ssl=true"
database => "mydatabase"
collection => "mycollection"
id => "myid"
}
}
}
That doesnt work and in mongodb log i see that the server tells "requires ssl".
The text was updated successfully, but these errors were encountered: