[COMPASS-3965] SRV URL authdb parsing issue (non-Atlas use case) Created: 15/Nov/19  Updated: 29/Oct/23  Resolved: 04/Feb/20

Status: Closed
Project: Compass
Component/s: Compass, Connectivity
Affects Version/s: 1.19.2
Fix Version/s: 1.21.0

Type: Bug Priority: Major - P3
Reporter: Luke Prochazka Assignee: Lucas Hrabovsky (Inactive)
Resolution: Fixed Votes: 1
Labels: srv
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Windows


Issue Links:
Depends
depends on COMPASS-3991 Update to node driver 3.3.5 Closed
Related
related to COMPASS-3096 authentication database picked up fro... Closed
Sprint: Iteration Tarantula, Iteration Urial, Iteration Vicuña

 Description   

Use case:  Non-Atlas SRV with per-DB auth.

In this case, the self constructed TXT records do no contain the authSource parameter, but is supplied on the connecting URI.

For Compass, we need to specify this as the authentication database.  Compass errors out with an authentication error, and the mongod.log clearly indicates a malformed auth request suggesting Compass is ignoring the authdb when SRV is enabled "UserNotFound: Could not find user user@admin" where admin is not expected.

Additionally, the SRV documentation states:

You can override the options specified in a TXT record by passing the option in the query string. In the following example, the query string has provided an override for the authSource option configured in the TXT record of the DNS entry above.


Generated at Wed Feb 07 22:34:49 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.