SQL-2919: Support passing in X509 PEM contents as password #368
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
mattChiaravalloti
requested changes
Aug 26, 2025
src/integration-test/java/com/mongodb/jdbc/integration/AuthX509IntegrationTest.java
Outdated
Show resolved
Hide resolved
src/test/java/com/mongodb/jdbc/utils/X509AuthenticationTest.java
Outdated
Show resolved
Hide resolved
Co-authored-by: Matthew Chiaravalloti <[email protected]>
Co-authored-by: Matthew Chiaravalloti <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Adding support to pass in full PEM contents into password field. This will help for adding X509 support for Tableau Server, which is planned to be tested in SQL-2924.
If the PEM Path is set it will take precedence. Otherwise attempt to use the
passwordproperty as PEM contents.I verified that it connects via Tableau Desktop using both the unencrypted (raw PEM contents) and encrypted (passing in JSON with
pemandpassphrasekeys).