Uploaded image for project: 'Go Driver'
  1. Go Driver
  2. GODRIVER-831

GSSAPI Authentication starts SASL conversation wrong

XMLWordPrintableJSON

    • Type: Icon: Bug Bug
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 1.0.0-rc1
    • Affects Version/s: None
    • Component/s: Authentication
    • None

      GSSAPI Authentication is beginning the SASL conversation with an empty payload.

      In 3.6 and before, MongoDB would return 

      { "conversationId" : 1, "done" : false, "payload" : new BinData(0, ""), "ok" : 1.0 }

      for an empty saslStart payload.

      In 4.0, MongoDB passes the empty client payload per SASL spec to Kerberos which starts negotiation.

      If the Go driver does start calling saslStart with a non-empty payload, this is compatible with all versions of MongoDB.

            Assignee:
            jeff.yemin@mongodb.com Jeffrey Yemin
            Reporter:
            jeff.yemin@mongodb.com Jeffrey Yemin
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: