client-api: Fix the signing key uploading endpoint

Uploading signing keys requires auth using UIAA, the error has thus been
changed to the UiaaResponse.

Uploading signing keys also fails under Synapse when using the /r0 API
path, using the /unstable path succeeds.
This commit is contained in:
poljar 2020-10-26 13:16:34 +01:00 committed by GitHub
parent f2a78babbd
commit c0eee62431
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23

View File

@ -3,14 +3,14 @@
use ruma_api::ruma_api;
use super::CrossSigningKey;
use crate::r0::uiaa::{AuthData, IncomingAuthData};
use crate::r0::uiaa::{AuthData, IncomingAuthData, UiaaResponse};
ruma_api! {
metadata: {
description: "Publishes cross signing keys for the user.",
method: POST,
name: "upload_signing_keys",
path: "/_matrix/client/r0/keys/device_signing/upload",
path: "/_matrix/client/unstable/keys/device_signing/upload",
rate_limited: false,
authentication: AccessToken,
}
@ -39,7 +39,7 @@ ruma_api! {
#[derive(Default)]
response: {}
error: crate::Error
error: UiaaResponse
}
impl Request<'_> {