From 748ed8f7c41378a35bf1d311ad6998ba86667947 Mon Sep 17 00:00:00 2001 From: Timm Friebe Date: Fri, 18 Aug 2023 13:50:37 +0200 Subject: [PATCH] Release 1.15.0 --- ChangeLog.md | 7 +++++++ README.md | 2 +- 2 files changed, 8 insertions(+), 1 deletion(-) diff --git a/ChangeLog.md b/ChangeLog.md index b3ad144..e1278a8 100755 --- a/ChangeLog.md +++ b/ChangeLog.md @@ -3,6 +3,13 @@ MongoDB for XP Framework ChangeLog ## ?.?.? / ????-??-?? +## 1.15.0 / 2023-08-18 + +* Merged PR #37: Support authentication mechanism negotiation. This way, + we default to using SCRAM-SHA-256 if the server supports it as mandated + by the specification. + (@thekid) + ## 1.14.0 / 2023-08-17 * Merged PR #37: Implement SCRAM-SHA-256 authentication. Implements #8 diff --git a/README.md b/README.md index a724122..29a30f0 100755 --- a/README.md +++ b/README.md @@ -111,7 +111,7 @@ Authentication -------------- To authenticate, pass username and password via the connection string, e.g. `mongodb://user:pass@localhost`. The authentication source defaults to *admin* but can be set by supplying a path, e.g. `mongodb://user:pass@localhost/test`. -Both *SCRAM-SHA-256* and *SCRAM-SHA-1* are supported as authentication mechanisms. By default, sha1 is used, as this is compatible with both local MongoDB installations as well as MongoDB Atlas. To change the mechanism, pass it as part of the connection string, e.g. `mongodb://user:pass@localhost?authMechanism=SCRAM-SHA-256`. +Both *SCRAM-SHA-256* and *SCRAM-SHA-1* are supported as authentication mechanisms. Which one is used is negotiated upon connecting with the server / cluster. To explicitely select the authentication mechanism, pass it as part of the connection string, e.g. `mongodb://user:pass@localhost?authMechanism=SCRAM-SHA-256`. SSL / TLS ---------