char
/
dendrite
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity
dendrite/keyserver
History
Kegsay a2174d3294
Implement /keys/changes (#1232) 
* Implement /keys/changes

And refactor QueryKeyChanges to accept a `to` offset.

* Unbreak tests

* Sort keys when serialising log tokens
 		2020-07-30 14:52:21 +01:00
..
api Implement /keys/changes (#1232) 2020-07-30 14:52:21 +01:00
internal Implement /keys/changes (#1232) 2020-07-30 14:52:21 +01:00
inthttp Add QueryKeyChanges (#1228) 2020-07-28 18:25:16 +01:00
producers Hook up device list updates to the sync notifier (#1231) 2020-07-30 11:15:46 +01:00
storage Implement /keys/changes (#1232) 2020-07-30 14:52:21 +01:00
README.md Add boilerplate for key server APIs (#1196) 2020-07-13 16:02:35 +01:00
keyserver.go Persist partition|offset|user_id in the keyserver (#1226) 2020-07-28 17:38:30 +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.