Don't explain how the IS might accept a 3pid
The IS is bound to it's own set of specifications, and if the client chose this API then they should be aware of the risks but not necessarily arbitrary alternatives.
This commit is contained in:
parent
63fdd72f73
commit
60dd9231e0
1 changed files with 2 additions and 4 deletions
|
@ -218,8 +218,7 @@ paths:
|
||||||
403:
|
403:
|
||||||
description: |-
|
description: |-
|
||||||
The homeserver does not permit the user from having the third party
|
The homeserver does not permit the user from having the third party
|
||||||
identifier as a contact option. This does not prevent the identity
|
identifier as a contact option.
|
||||||
service from binding the third party identifier, however.
|
|
||||||
schema:
|
schema:
|
||||||
$ref: "definitions/errors/error.yaml"
|
$ref: "definitions/errors/error.yaml"
|
||||||
examples:
|
examples:
|
||||||
|
@ -273,8 +272,7 @@ paths:
|
||||||
403:
|
403:
|
||||||
description: |-
|
description: |-
|
||||||
The homeserver does not permit the user from having the third party
|
The homeserver does not permit the user from having the third party
|
||||||
identifier as a contact option. This does not prevent the identity
|
identifier as a contact option.
|
||||||
service from binding the third party identifier, however.
|
|
||||||
schema:
|
schema:
|
||||||
$ref: "definitions/errors/error.yaml"
|
$ref: "definitions/errors/error.yaml"
|
||||||
examples:
|
examples:
|
||||||
|
|
Loading…
Add table
Add a link
Reference in a new issue