Skip to content

Conversation

@rjrudin
Copy link
Contributor

@rjrudin rjrudin commented Aug 16, 2023

Made a couple of small improvements to how errors are reported for a couple of the scenarios in this test too.

Removed ignored/obsolete test for certificate auth that I could never get to work.

@rjrudin rjrudin force-pushed the feature/2way-ssl-test branch 2 times, most recently from 0f4032b to d2ec51e Compare August 16, 2023 21:44
Made a couple of small improvements to how errors are reported for a couple of the scenarios in this test too.

Removed ignored/obsolete test for certificate auth that I could never get to work.
@rjrudin rjrudin force-pushed the feature/2way-ssl-test branch from d2ec51e to 287387d Compare August 17, 2023 17:06
throw new MarkLogicIOException(String.format("SSL error occurred: %s; ensure you are using a valid certificate " +
"if the MarkLogic app server requires a client certificate for SSL.", message));
}
}
Copy link
Contributor

Choose a reason for hiding this comment

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

So, if e is an SSL Exception but doesn't contain readHandshakeRecord, then we're good with the normal MarkLogicIOException?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Right - I was getting the normal MarkLogicIOException originally, and felt like this was a special case where it'd be helpful to mention checking the use of certificates when "readHandshakeRecord" is in the error message.

@rjrudin rjrudin merged commit b9aa2e3 into develop Aug 18, 2023
@rjrudin rjrudin deleted the feature/2way-ssl-test branch August 18, 2023 15:43
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.

3 participants