Summary

When starting a standalone with auth and ssl using run-mongodb.sh authentication is not enforced. This may cause failures for tests expecting authentication error.

This bug was hidden because run-orchestration.sh uses the mongo-orchestration HTTP API, which internally added --auth to mongod whenever login/password were present in the config, regardless of auth_key. run-mongodb.sh bypasses mongo-orchestration and passes the config directly to mongodb-runner, which does not have this implicit behavior and relies solely on what is in the config file.

Motivation

Who is the affected end user?

Drivers developers

How does this affect the end user?

Not affected

How likely is it that this problem or use case will occur?

If a driver has tests that expect authentication enforced on a standalone

If the problem does occur, what are the consequences and how severe are they?

Test failures

Is this issue urgent?

No

Is this ticket required by a downstream team?

No

Is this ticket only for tests?

Yes

Acceptance Criteria

Bug is fixed and the fix is tested.