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

[elasticsearch] allow defining multiple ca certs #5246

Merged
merged 1 commit into from
Oct 30, 2015

Conversation

spalger
Copy link
Contributor

@spalger spalger commented Oct 30, 2015

Fixes #5212

In the event that a user needs to configure multiple files for a CA chain the configuration
will now accept either a single string or array for elasticsearch.ssl.ca and then convert
that value to always be an array.

In the event that a user needs to configure multiple files for a CA chain the configuration
will now accept either a single string or array for `elasticsearch.ssl.ca` and then convert
that value to always be an array.
@jbudz
Copy link
Member

jbudz commented Oct 30, 2015

LGTM

@jbudz jbudz assigned spalger and unassigned jbudz Oct 30, 2015
@simianhacker
Copy link
Member

LGTM (tested it with my certs)

spalger added a commit that referenced this pull request Oct 30, 2015
[elasticsearch] allow defining multiple ca certs
@spalger spalger merged commit 89ae862 into elastic:master Oct 30, 2015
@tbragin tbragin mentioned this pull request Nov 3, 2015
9 tasks
@spalger spalger deleted the implement/multipleCas branch February 25, 2016 22:46
@epixa
Copy link
Contributor

epixa commented Apr 13, 2016

@spalger @simianhacker We probably should do this for the kibana ssl cert as well, what do you guys think? I don't think it's possible to use a cert chain on the browser ssl config.

@spalger
Copy link
Contributor Author

spalger commented Apr 14, 2016

yeah, pretty sure you have to specify a specific cert to use to but IDK

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

Successfully merging this pull request may close these issues.

4 participants