Update 3983-sending-otk-claims-to-appservices.md

travis/msc/enc-as/otk-query
Travis Ralston 1 year ago committed by GitHub
parent 2177b93907
commit 052d4800f2
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23

@ -107,7 +107,7 @@ for the user.
**TODO**: This is probably best as its own MSC. **TODO**: This is probably best as its own MSC.
Independent of the appservice having `/keys/claim` proxied to it, it may be desireable for both the Independent of the appservice having `/keys/claim` proxied to it, it may be desirable for both the
fallback and one-time key to be returned. Servers should *always* include the fallback key alongside fallback and one-time key to be returned. Servers should *always* include the fallback key alongside
the requested OTKs. When using this proposal's new endpoint, the server should use the fallback key the requested OTKs. When using this proposal's new endpoint, the server should use the fallback key
from the appservice's response rather than a previously stored fallback key, if present (if the from the appservice's response rather than a previously stored fallback key, if present (if the
@ -121,6 +121,8 @@ do upon first (known) use.
Clients can determine which of the keys returned is the fallback key by `fallback: true` on the returned Clients can determine which of the keys returned is the fallback key by `fallback: true` on the returned
keys. keys.
Servers MUST NOT mark the fallback key as "used" unless no other OTKs are returned.
## Potential issues ## Potential issues
As described, the appservice could be offline or in fact experience a worse uptime than the homeserver. As described, the appservice could be offline or in fact experience a worse uptime than the homeserver.

Loading…
Cancel
Save