Skip to content

docs: fix small error #2025

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
martin-g merged 1 commit into from
Dec 19, 2022
+2 −2
Merged

docs: fix small error #2025

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions doc/content/en/docs/++version++/SASL profile/_index.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -31,7 +31,7 @@ SASL ([RFC 2222](https://www.ietf.org/rfc/rfc2222.txt)) provides a framework for
## Overview
SASL negotiation proceeds as a series of message interactions over a connection between a client and server using a selected SASL mechanism. The client starts this negotiation by sending its chosen mechanism name with an initial (possibly empty) message. Negotiation proceeds with the exchange of messages until either side indicates success or failure. The content of the messages is mechanism-specific. If the negotiation succeeds, then the session can proceed over the connection, otherwise it must be abandoned.

Some mechanisms continue to process session data after negotiation (e.g., encrypting it), while some specify that further session data is transmitted unmodifed.
Some mechanisms continue to process session data after negotiation (e.g., encrypting it), while some specify that further session data is transmitted unmodified.

## Negotiation

Expand All @@ -41,7 +41,7 @@ Avro SASL negotiation uses four one-byte commands.
* 0: START Used in a client's initial message.
* 1: CONTINUE Used while negotiation is ongoing.
* 2: FAIL Terminates negotiation unsuccessfully.
* 3: COMPLETE Terminates negotiation sucessfully.
* 3: COMPLETE Terminates negotiation successfully.

The format of a START message is:

Expand Down