You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When connecting to OpenSearch via https it would be nice to configure in properties which SSL Bundle to use. There already seem to be some properties for this:
But unless I'm doing something wrong the bundle is not used, maybe those properties are just there because OpenSearchProperties uses Restclient properties from Elasticsearch.
For this configuration to work I had to create custom RestClientBuilderCustomizer with something like this:
Is your feature request related to a problem?
When connecting to OpenSearch via https it would be nice to configure in properties which SSL Bundle to use. There already seem to be some properties for this:
But unless I'm doing something wrong the bundle is not used, maybe those properties are just there because
OpenSearchProperties
usesRestclient
properties from Elasticsearch.For this configuration to work I had to create custom
RestClientBuilderCustomizer
with something like this:Maybe this should be part of
OpenSearchRestClientConfigurations
, applied by theDefaultRestClientBuilderCustomizer
or set as part ofopensearchRestClientBuilder
? Elasticsearch autoconfiguration is doing something similar here - https://github.com/spring-projects/spring-boot/blob/v3.4.0/spring-boot-project/spring-boot-autoconfigure/src/main/java/org/springframework/boot/autoconfigure/elasticsearch/ElasticsearchRestClientConfigurations.java#L97.What solution would you like?
Configure
opensearch.restclient.ssl.bundle
without needing to create any additionalRestClientBuilderCustomizer
's .What alternatives have you considered?
Create
RestClientBuilderCustomizer
or add my OpenSearch CA to global trust store (probably would work, but didn't try, don't really want to do that).Do you have any additional context?
If this makes sense and looks reasonable I can try creating PR for this.
The text was updated successfully, but these errors were encountered: