You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jun 23, 2022. It is now read-only.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
When a rpc connection is established, if the configuration of open_auth is true, we should start negotiation by creating a negotiation instance for both server rpc_session and client rpc_session.
Especially for client rpc_session, we should change the connect state to SS_NEGOTIATION, which means we are doing security authentication.
Could you please explain the negotiation process with its function or structure to me? For example, when open_auth is true, should create negotiation with both client and server rpc session, client will turn its state to SS_NEGOTIATION, then start to negotiation by function start_negotiate. How about server rpc session, when will server call function start_negotiate?
Besides, is the SS_NEGOTIATION only used for client session?
Could you please explain the negotiation process with its function or structure to me? For example, when open_auth is true, should create negotiation with both client and server rpc session, client will turn its state to SS_NEGOTIATION, then start to negotiation by function start_negotiate. How about server rpc session, when will server call function start_negotiate?
Besides, is the SS_NEGOTIATION only used for client session?
Server need to call start_negotiation to create server_negotiation and change it's state to SASL_LIST_MECHANISMS.
All states in session_state is only used by client, including session_state, to do some state judgement.
Here is the negotiation process, And I will add it in the next pull request:
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
When a rpc connection is established, if the configuration of
open_auth
is true, we should start negotiation by creating a negotiation instance for both server rpc_session and client rpc_session.Especially for client rpc_session, we should change the connect state to
SS_NEGOTIATION
, which means we are doing security authentication.New configuration added
[security] + enable_auth = false