Details
-
Bug
-
Resolution: Fixed
-
Major - P3
-
None
-
None
Description
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.
Attachments
Issue Links
- related to
-
CSHARP-2366 GSSAPI Authentication starts SASL conversation wrong
-
- Closed
-
-
GODRIVER-818 Go driver does not respect KRB5CCNAME environment variable
-
- Closed
-