You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
+ The driver’s default configuration for encrypted is now false (meaning that driver will only attempt plain text connections by default).
59
+
60
+
+ Connections to encrypted services (such as Neo4j Aura) should now explicitly be set to encrypted.
61
+
62
+
+ When encryption is explicitly enabled, the default trust mode is to trust the CAs that are trusted by operating system and use hostname verification.
63
+
64
+
+ This means that encrypted connections to servers holding self-signed certificates will now fail on certificate verification by default.
65
+
66
+
+ Using the new `neo4j+ssc` scheme will allow to connect to servers holding self-signed certificates and not use hostname verification.
67
+
68
+
+ The `neo4j://` scheme replaces `bolt+routing://` and can be used for both clustered and single-instance configurations with Neo4j 4.0.
69
+
70
+
71
+
72
+
See, https://neo4j.com/docs/migration-guide/4.0/upgrade-driver/#upgrade-driver-breakingchanges
73
+
74
+
75
+
See, https://neo4j.com/docs/driver-manual/current/client-applications/#driver-connection-uris for changes in default security settings between 3.x and 4.x
76
+
77
+
78
+
Connecting with Python Driver 4.0 against Neo4j 3.5
0 commit comments