IT4Change/gradido
3
0
Fork 0
mirror of https://github.com/IT4Change/gradido.git synced 2026-01-18 10:51:23 +00:00
Code Issues Packages Projects Releases Wiki Activity

Update docu/Concepts/TechnicalRequirements/Federation.md

Browse Source 
Co-authored-by: Ulf Gebhardt <ulf.gebhardt@webcraft-media.de>
This commit is contained in:
clauspeterhuebner 2023-02-27 12:35:45 +01:00 committed by GitHub
parent d3a1b8afe5
commit 73ce450344
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
docu/Concepts/TechnicalRequirements/Federation.md
View File

@ -34,7 +34,7 @@ As soon as a Gradido Community is up and running the DHT-Modul first write the h
The up and running Backend-Modul contains a validation logic to verify the community entries from the own DHT-Modul. For each announced but unverified community-entry the GraphQL-Client is used to invoke a getPublicKey-Request. Depending on the containing api-version the matching GraphQL-Client is used and the getPublicKey-Request will be send to the given URL.
As soon as the FederationModul of the assoziated community received the getPublicKey-request the own publicKey is read from database and send back in the response.
As soon as the FederationModul of the associated community received the getPublicKey-request the own publicKey is read from database and send back in the response.
The GraphQL-Client will read from the returned response data the publicKey of the other community and compare it with the data of the community-entry, which cause the getPublicKey-Request. If they match the community-entry will be updated be inserting the current timestamp in the verifiedAt-field of this community-entry.