Skip to content

Conversation

@rjrudin
Copy link
Contributor

@rjrudin rjrudin commented Jan 26, 2023

These fixes are driven by testing against the ReverseProxyServer which can now emulate ML Cloud. The fixes:

  1. If user chooses an sslProtocol of "default", then the JVM's default trust manager will be used as well.
  2. If the user uses withMarkLogicCloudAuth, then the SSL protocol will default to "default".
  3. The call to "/token" in ML Cloud now uses the user-provided SSL hostname verifier (this was not required on the ML Cloud instance I tested with, but that is not guaranteed to be true).

@rjrudin rjrudin requested a review from BillFarber January 26, 2023 18:11
@rjrudin rjrudin force-pushed the feature/cloud-reverse-proxy branch from b16971a to f555016 Compare January 26, 2023 18:17
These fixes are driven by testing against the ReverseProxyServer which can now emulate ML Cloud. The fixes:

1. If user chooses an sslProtocol of "default", then the JVM's default trust manager will be used as well.
2. If the user uses `withMarkLogicCloudAuth`, then the SSL protocol will default to "default".
3. The call to "/token" in ML Cloud now uses the user-provided SSL hostname verifier (this was not required on the ML Cloud instance I tested with, but that is not guaranteed to be true).
@rjrudin rjrudin force-pushed the feature/cloud-reverse-proxy branch from f555016 to ddcd6fc Compare January 26, 2023 19:28
Copy link
Contributor

@BillFarber BillFarber left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@rjrudin rjrudin merged commit 4c63194 into develop Jan 27, 2023
@rjrudin rjrudin deleted the feature/cloud-reverse-proxy branch January 27, 2023 00:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants