Details
-
Task
-
Resolution: Fixed
-
Major - P3
-
None
-
None
-
None
Description
Description:
No documentation summary in engineering ticket
Scope of changes:
- isMaster

- db.auth

- copydb

- relnotes 4.0

- note:: don't need to update the db.isMaster since it just runs isMaster without any optional fields.
Impact to other docs outside of this product:
none
MVP:
Resources:
Engineering Ticket Description:
Allow clients to inform servers during isMaster which user they will eventually authenticate as. This permits the server to express which SASL authentication mechanisms may be used to authenticate as that user. The username send in the command request must be unprocessed and unnormalized.
Example:
MongoDB Enterprise > db.runCommand({isMaster: 1, saslSupportedMechs: "sajack.admin"})
|
{
|
"ismaster" : true,
|
"saslSupportedMechs": ["SCRAM-SHA-1", "SCRAM-SHA-256"],
|
...
|
"ok" : 1
|
}
|
|
Attachments
Issue Links
- documents
-
SERVER-32965 Expose per-user SASL mechanism negotiation via isMaster
-
- Closed
-
- is related to
-
DOCS-11683 Update auth mechanism references for SCRAM-SHA-256
-
- Closed
-