Expose per-user SASL mechanism negotiation via isMaster

XMLWordPrintableJSON

    • Type: Improvement
    • Resolution: Fixed
    • Priority: Major - P3
    • 3.7.2
    • Affects Version/s: None
    • Component/s: Security
    • None
    • Fully Compatible
    • Platforms 2018-02-12
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      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
      }
      
      

            Assignee:
            Spencer Jackson
            Reporter:
            Spencer Jackson
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: