archive
/
matrix-spec
mirror of https://github.com/matrix-org/matrix-spec
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Apply suggestions from code review

Browse Source 
Co-Authored-By: Matthew Hodgson <matthew@matrix.org>
pull/977/head
Travis Ralston 5 years ago committed by GitHub
parent 4e43024039
commit 6d5e90b1d6
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File

6
proposals/2263-homeserver-pw-resets.md
Unescape Escape View File

@ -1,6 +1,6 @@
# MSC2263: Give homeservers the ability to handle their own 3PID registrations/password resets # MSC2263: Give homeservers the ability to handle their own 3PID registrations/password resets
In order to better protect the privacy of of a user, Matrix is wanting to shift to In order to better protect the privacy of a user, Matrix is wanting to shift to
a model where identity servers have less control over the affairs of the homeserver. a model where identity servers have less control over the affairs of the homeserver.
Identity servers are currently used to reset the passwords of users on a given homeserver Identity servers are currently used to reset the passwords of users on a given homeserver
as an identity verification technique, however there is no reason why the homeserver as an identity verification technique, however there is no reason why the homeserver
@ -15,7 +15,7 @@ The `id_server` parameter is to become optional on the following endpoints:
* `/_matrix/client/:version/register/:medium/requestToken` * `/_matrix/client/:version/register/:medium/requestToken`
* `/_matrix/client/:version/account/password/:medium/requestToken` * `/_matrix/client/:version/account/password/:medium/requestToken`
The `id_server` parameter is additionally deprecated with intentions of being removed The `id_server` parameter is additionally deprecated with intention of being removed
in a future specification release on the `/register/:medium` and `/account/password/:medium` in a future specification release on the `/register/:medium` and `/account/password/:medium`
endpoints. Once appropriate adoption has been achieved, the specification can safely endpoints. Once appropriate adoption has been achieved, the specification can safely
remove the parameter as supported. The reason for this deprecation is to completely remove the parameter as supported. The reason for this deprecation is to completely
@ -23,7 +23,7 @@ remove the identity server's ability to be involved in password resets/registrat
Users wishing to bind their 3rd party identifiers can do so after registration, and Users wishing to bind their 3rd party identifiers can do so after registration, and
clients can automate this if they so desire. clients can automate this if they so desire.
Similarly, `bind_email` and `bind_msisdn` are deprecated with intentions to be removed Similarly, `bind_email` and `bind_msisdn` are deprecated with intention to be removed
in a future specification version on `/register`. The flags have no effect if no `id_server` in a future specification version on `/register`. The flags have no effect if no `id_server`
is being used. is being used.

Write Preview
Loading…
Cancel
Save