pub enum Event {
GreetingSent {
greeting: Greeting<'static>,
},
ResponseSent {
handle: ResponseHandle,
response: Response<'static>,
},
CommandReceived {
command: Command<'static>,
},
CommandAuthenticateReceived {
command_authenticate: CommandAuthenticate,
},
AuthenticateDataReceived {
authenticate_data: AuthenticateData<'static>,
},
IdleCommandReceived {
tag: Tag<'static>,
},
IdleDoneReceived,
}
Variants§
GreetingSent
Initial `Greeting was sent successfully.
ResponseSent
Enqueued Response
was sent successfully.
Fields
handle: ResponseHandle
Handle of the formerly enqueued Response
.
CommandReceived
Command received.
CommandAuthenticateReceived
Command AUTHENTICATE received.
Note: The server MUST call Server::authenticate_continue
(if it needs more data for
authentication) or Server::authenticate_finish
(if there already is enough data for
authentication) next. “Enough data” is determined by the used SASL mechanism, if there was
an initial response (SASL-IR), etc.
Fields
command_authenticate: CommandAuthenticate
AuthenticateDataReceived
Continuation to AUTHENTICATE received.
Note: The server MUST call Server::authenticate_continue
(if it needs more data for
authentication) or Server::authenticate_finish
(if there already is enough data for
authentication) next. “Enough data” is determined by the used SASL mechanism, if there was
an initial response (SASL-IR), etc.
Note, too: The client may abort the authentication by using AuthenticateData::Cancel
.
Make sure to honor the client’s request to not end up in an infinite loop. It’s up to the
server to end the authentication flow.
Fields
authenticate_data: AuthenticateData<'static>