Fix `POST _matrix/federation/v1/user/keys/claim` response schema (#1351)

The syntax was not compliant with the Swagger spec.
It also lacked one level of nesting.

Signed-off-by: Kévin Commaille <zecakeh@tedomum.fr>
pull/1355/head
Kévin Commaille 2 years ago committed by GitHub
parent b2c4abf567
commit dfc8a2e184
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23

@ -0,0 +1 @@
Fix `POST _matrix/federation/v1/user/keys/claim` response schema.

@ -76,29 +76,32 @@ paths:
See the [Client-Server Key Algorithms](/client-server-api/#key-algorithms) section for more information on
the Key Object format.
# User
additionalProperties:
type: object
# Device
additionalProperties:
type:
- string
- type: object
title: KeyObject
properties:
key:
type: string
description: The key, encoded using unpadded base64.
signatures:
type: object
# Key
additionalProperties:
type: object
title: KeyObject
properties:
key:
type: string
description: The key, encoded using unpadded base64.
signatures:
type: object
title: Signatures
additionalProperties:
type: object
title: Signatures
additionalProperties:
type: object
additionalProperties:
type: string
description: |-
Signature of the key object.
type: string
description: |-
Signature of the key object.
The signature is calculated using the process described at [Signing JSON](/appendices/#signing-json).
required: ['key', 'signatures']
The signature is calculated using the process described at [Signing JSON](/appendices/#signing-json).
required: ['key', 'signatures']
example: {
"@alice:example.com": {
"JLAFKJWSCS": {

Loading…
Cancel
Save