Uploaded image for project: 'Documentation'
  1. Documentation
  2. DOCS-11655

Docs for SERVER-32965: Expose per-user SASL mechanism negotiation via isMaster

    XMLWordPrintableJSON

Details

    • Icon: Task Task
    • Resolution: Fixed
    • Icon: Major - P3 Major - P3
    • 3.7.2
    • 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

        Activity

          People

            kay.kim@mongodb.com Kay Kim (Inactive)
            kay.kim@mongodb.com Kay Kim (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:
              5 years, 38 weeks, 2 days ago