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:
Travis Ralston 2018-08-31 11:26:28 -06:00
parent 63fdd72f73
commit 60dd9231e0

View file

@ -218,8 +218,7 @@ paths:
403:
description: |-
The homeserver does not permit the user from having the third party
identifier as a contact option. This does not prevent the identity
service from binding the third party identifier, however.
identifier as a contact option.
schema:
$ref: "definitions/errors/error.yaml"
examples:
@ -273,8 +272,7 @@ paths:
403:
description: |-
The homeserver does not permit the user from having the third party
identifier as a contact option. This does not prevent the identity
service from binding the third party identifier, however.
identifier as a contact option.
schema:
$ref: "definitions/errors/error.yaml"
examples: