feat: [DBOPS-825]: MongoDB TLS #11
Open
Conversation
This file contains 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
hemanthbsridhar
force-pushed
the
feat/DBOPS-825
branch
3 times, most recently
from
08323d9 to
b69cfbf
Compare
hemanthbsridhar
force-pushed
the
feat/DBOPS-825
branch
from
b69cfbf to
0e70af1
Compare
hemanthbsridhar
changed the title
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.
Given a mongo connection with tls / mtls configuration,
When we connect and run through liquibase command,
we should be able to connect successfully and run the commands.
New libraries added
Changes
- /etc/ssl/certs/dbops/client.crt
- /etc/ssl/certs/dbops/client.key
that is used to generate /etc/ssl/certs/dbops/client.p12( pkcs12 ) which gets imported to the default jvm keyStore ( ${JAVA_HOME}/lib/security/jssecacerts )