[DRIVERS-808] Specify behavior of empty authSource URI option Created: 30/Jan/20  Updated: 05/Aug/21

Status: Implementing
Project: Drivers
Component/s: None
Fix Version/s: None

Type: Improvement Priority: Major - P3
Reporter: John Stewart (Inactive) Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on CDRIVER-3517 Specify behavior of empty authSource ... Backlog
depends on CXX-1927 Specify behavior of empty authSource ... Backlog
depends on PHPC-1548 Specify behavior of empty authSource ... Blocked
depends on CSHARP-2922 Specify behavior of empty authSource ... Closed
depends on GODRIVER-1479 Specify behavior of empty authSource ... Closed
depends on JAVA-3617 Specify behavior of empty authSource ... Closed
depends on MOTOR-499 Specify behavior of empty authSource ... Closed
depends on NODE-2443 Specify behavior of empty authSource ... Closed
depends on PYTHON-2113 Specify behavior of empty authSource ... Closed
depends on RUBY-2112 Specify behavior of empty authSource ... Closed
depends on RUST-502 Specify behavior of empty authSource ... Closed
Driver Compliance:
Key Status/Resolution FixVersion
PHPC-1548 Blocked
NODE-2443 Done 4.4.0
MOTOR-499 Won't Do
CDRIVER-3517 Backlog
PYTHON-2113 Fixed 3.11
GODRIVER-1479 Fixed 1.5.0
CXX-1927 Backlog
JAVA-3617 Fixed 4.1.0
CSHARP-2922 Fixed 2.11.0
RUBY-2112 Done
RUST-502 Fixed 1.1.0
SWIFT-1298 Won't Do

 Description   

As far as I can tell there is no language in the URI spec defining how a present but empty authSource in the URI should be handled, nor does there appear to be a test for this situation. Can this case be explicitly specified?

It may be convenient for users to treat an empty authSource the same way as if authSource was not provided at all. This is also in line with common web development conventions.


Generated at Thu Feb 08 08:22:25 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.