Add the fallback logic to use 'ssl_engine' if 'ssl_handler' attribute is not available / compatible #5667
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Originally was posted on the OpenSearch forum [1], when
transport-reactor-netty4plugin is activated, some functionality related toopensearch-securityplugin is not working properly.It turned out the that issue was related to the
SslHandlerthatopensearch-securitytries to locate by name. Thetransport-reactor-netty4plugin does use different naming convention and as such, theSslHandlerhas not being detected. Further testing uncovered that merely returningSslHandlermay not be enough due to classloader issues (we have at least 3 places whereSslHandlercould be loaded from):To address that, adding the fallback attribute
ssl_enginethat return the instance of theSSLEnginedirectly (if available) since theSslHandleris not really needed. The fix works as expected, the output is identical to the default transport (netty4):[1] https://forum.opensearch.org/t/pods-not-coming-up-after-using-transport-reactor-netty4-plugin-for-mcp-server/26990
Issues Resolved
Complimentary to opensearch-project/OpenSearch#19458, see please https://forum.opensearch.org/t/pods-not-coming-up-after-using-transport-reactor-netty4-plugin-for-mcp-server/26990
Testing
Tested SNAPSHOT distribution, default implementation (netty4) is not affected
Check List
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.