1f349/dendrite
1
0
Fork 0
mirror of https://github.com/1f349/dendrite.git synced 2024-09-20 02:46:34 +01:00
Code Issues Packages Projects Releases Wiki Activity
6b6b420b9f
dendrite/keyserver
History
Till 081f5e7226
Update database migrations, remove goose (#2264) 
* Add new db migration

* Update migrations
Remove goose

* Add possibility to test direct upgrades

* Try to fix WASM test

* Add checks for specific migrations

* Remove AddMigration
Use WithTransaction
Add Dendrite version to table

* Fix linter issues

* Update tests

* Update comments, outdent if

* Namespace migrations

* Add direct upgrade tests, skipping over one version

* Split migrations

* Update go version in CI

* Fix copy&paste mistake

* Use contexts in migrations

Co-authored-by: kegsay <kegan@matrix.org>
Co-authored-by: Neil Alexander <neilalexander@users.noreply.github.com>
2022-07-25 10:39:22 +01:00
..
api Add InputDeviceListUpdate to the keyserver, remove old input API (#2536) 2022-06-15 14:27:07 +01:00
consumers Add InputDeviceListUpdate to the keyserver, remove old input API (#2536) 2022-06-15 14:27:07 +01:00
internal Add InputDeviceListUpdate to the keyserver, remove old input API (#2536) 2022-06-15 14:27:07 +01:00
inthttp Add InputDeviceListUpdate to the keyserver, remove old input API (#2536) 2022-06-15 14:27:07 +01:00
producers Remove eduserver (#2306) 2022-03-29 14:14:35 +02:00
storage Update database migrations, remove goose (#2264) 2022-07-25 10:39:22 +01: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.