Config encryption and trust strategy via connection URI scheme #390
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
gjmwoods
approved these changes
Mar 5, 2020
Added new URI scheme support. Beside `bolt` and `neo4j`, we also support `+s` for connecting with encryption and chain trust strategy. And `+ssc` for connecting with encyption but insecure trust strategy. When configuring encryption and trust both via uri and config, an error will be generated instead.
zhenlineo
force-pushed
the
4.0-use-url-to-config-encryption-and-trust
branch
from
b565d7e
to
efe1a03
Compare
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.
Added new URI scheme support. Beside
boltandneo4j, we also support+sfor connecting with encryption and chain trust strategy.And
+sscfor connecting with encyption but insecure trust strategy.When configuring encryption and trust both via uri and config, an error will be generated instead.