GROUP-105 Moved certificate to resources, added Spring SSL bundle #40
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
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.
Description of Changes
Reverted previous Dockerfile changes. While it worked for helping the database drivers find the certificate in the default spot, the Java runtime does not have the certificate included in it's trust store. This change uses a recently added feature in Spring 3.1 to add an SSL bundle (which I think adds the specified certs to the trust / key stores). The alternative would be to manually create SSL objects using the plain java.net SSL utilities.
PS: If this keeps being an issue, I may just set up a self-signed SSL Postgres instance on my computer. I planned to do this in the future for quicker feedback, but may have to do it earlier than expected.