1// SASLAuthenticate continues a sasl authentication flow. Prior to Kafka 1.0.0,
2// authenticating with sasl involved sending raw blobs of data back and forth.
3// After, those blobs are wrapped in a SASLAuthenticateRequest The benefit of
4// this wrapping is that Kafka can indicate errors in the response, rather than
5// just closing the connection. Additionally, the response allows for further
6// extension fields.
7SASLAuthenticateRequest => key 36, max version 2, flexible v2+
8 // SASLAuthBytes contains bytes for a SASL client request.
9 SASLAuthBytes: bytes
10
11// SASLAuthenticateResponse is returned for a SASLAuthenticateRequest.
12SASLAuthenticateResponse =>
13 // ErrorCode is a potential error.
14 ErrorCode: int16
15 // ErrorMessage can contain a message for an error.
16 ErrorMessage: nullable-string
17 // SASLAuthBytes is the server challenge continuing SASL flow.
18 SASLAuthBytes: bytes
19 // SessionLifetimeMillis, added in Kafka 2.2.0, is how long the SASL
20 // authentication is valid for. This timeout is only enforced if the request
21 // was v1. After this timeout, Kafka expects the next bytes on the wire to
22 // begin reauthentication. Otherwise, Kafka closes the connection.
23 SessionLifetimeMillis: int64 // v1+
View as plain text