mirror of
https://github.com/1f349/dendrite.git
synced 2024-11-08 18:16:59 +00:00
ec716793eb
* Initial federation sender -> federation API refactoring * Move base into own package, avoids import cycle * Fix build errors * Fix tests * Add signing key server tables * Try to fold signing key server into federation API * Fix dendritejs builds * Update embedded interfaces * Fix panic, fix lint error * Update configs, docker * Rename some things * Reuse same keyring on the implementing side * Fix federation tests, `NewBaseDendrite` can accept freeform options * Fix build * Update create_db, configs * Name tables back * Don't rename federationsender consumer for now |
||
---|---|---|
.. | ||
api | ||
consumers | ||
internal | ||
inthttp | ||
producers | ||
storage | ||
types | ||
keyserver.go | ||
README.md |
Key Server
This is an internal component which manages E2E keys from clients. It handles all the Key Management APIs with the exception of /keys/changes
which is handled by Sync API. This component is designed to shard by user ID.
Keys are uploaded and stored in this component, and key changes are emitted to a Kafka topic for downstream components such as Sync API.
Internal APIs
PerformUploadKeys
stores identity keys and one-time public keys for given user(s).PerformClaimKeys
acquires one-time public keys for given user(s). This may involve outbound federation calls.QueryKeys
returns identity keys for given user(s). This may involve outbound federation calls. This component may then cache federated identity keys to avoid repeatedly hitting remote servers.- A topic which emits identity keys every time there is a change (addition or deletion).
### Endpoint mappings
- Client API maps
/keys/upload
toPerformUploadKeys
. - Client API maps
/keys/query
toQueryKeys
. - Client API maps
/keys/claim
toPerformClaimKeys
. - Federation API maps
/user/keys/query
toQueryKeys
. - Federation API maps
/user/keys/claim
toPerformClaimKeys
. - Sync API maps
/keys/changes
to consuming from the Kafka topic.