1f349/dendrite
4
0
Fork 0
mirror of https://github.com/1f349/dendrite.git synced 2025-02-16 19:38:35 +00:00
Code Issues Packages Projects Releases Wiki Activity
dendrite/keyserver
History
Neil Alexander 5513f182cc
Enforce device list backoffs (#2653) 
This ensures that if the device list updater is already backing off a node, we don't try to call processServer again anyway for server just because the server name arrived in the channel. Otherwise we can keep trying to hit a remote server that is offline or not behaving every second and that spams the logs too.
2022-08-19 10:23:09 +01:00
..
api
Generic-based internal HTTP API (#2626)
2022-08-11 15:29:33 +01:00
consumers
Add InputDeviceListUpdate to the keyserver, remove old input API (#2536)
2022-06-15 14:27:07 +01:00
internal
Enforce device list backoffs (#2653)
2022-08-19 10:23:09 +01:00
inthttp
Generic-based internal HTTP API (#2626)
2022-08-11 15:29:33 +01:00
producers
Remove eduserver (#2306)
2022-03-29 14:14:35 +02:00
storage
Fix issues with migrations not getting executed (#2628)
2022-08-08 10:18:57 +02:00
types
Remove sarama/saramajetstream dependencies (#2138)
2022-02-04 13:08:13 +00:00
keyserver.go
Add InputDeviceListUpdate to the keyserver, remove old input API (#2536)
2022-06-15 14:27:07 +01:00
README.md
Add boilerplate for key server APIs (#1196)
2020-07-13 16:02:35 +01:00

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 to PerformUploadKeys.
  • Client API maps /keys/query to QueryKeys.
  • Client API maps /keys/claim to PerformClaimKeys.
  • Federation API maps /user/keys/query to QueryKeys.
  • Federation API maps /user/keys/claim to PerformClaimKeys.
  • Sync API maps /keys/changes to consuming from the Kafka topic.