add be1-go implemention of federation authentication part #1827
Conversation
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
…aining a FederationChallenge
Pull reviewers statsStats of the last 30 days for popstellar:
|
…t_schema' into work-be1-1florentin-federation_auth_protocol
…t_schema' into work-be1-1florentin-federation_auth_protocol
…ederation-authentication_a' into work-be1-1florentin-federation_auth_protocol
|
|
|
|
|
sgueissa
approved these changes
May 29, 2024
MariemBaccari
approved these changes
May 29, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Add handler for federation message that do the following (not including verification of sender/etc):
The channel "/root/<loa_id>/federation" is used for all the current messages.
The following description was from before the go refactor for the code with last commit: c6b307ff6ee4b4822514ac890e6ca2a2698e091d
Implements some message handlers of the federation authentication (FederationResult is being done by Florentin)- processChallengeRequest: generate a new challenge and send it back to the organizer
- processFederationExpect: Store informations about the other organization, with the expected challenge.
- processFederationInit: Store informations about the other organization, initiate a ws connection to the other server, then publish the FederationChallenge on the other server's federation channel
- processFederationChallenge: check that the challenge is valid, send federation result
A channel "/root/<lao_id>/federation" is created when a lao is created.
Informations about the other organization are stored in a map, such that it could be possible to handle multiple organizations. The public key of the organizer of the other lao is used as the key.
The challenge field of the json schema of FederationInit was changed from only a challenge to a general message containing a FederationChallenge. So that it's possible to send a FederationChallenge signed by the organizer (not the server)