From 9354461084c9aaea9da28b46fbb61dda7f247f71 Mon Sep 17 00:00:00 2001 From: Charles Wright Date: Tue, 1 Mar 2022 10:17:30 -0600 Subject: [PATCH] Removed proposed changes to /login Signed-off-by: Charles Wright --- proposals/3744-flexible-auth.md | 31 ++++--------------------------- 1 file changed, 4 insertions(+), 27 deletions(-) diff --git a/proposals/3744-flexible-auth.md b/proposals/3744-flexible-auth.md index f96bb51a8..889ea146a 100644 --- a/proposals/3744-flexible-auth.md +++ b/proposals/3744-flexible-auth.md @@ -18,6 +18,10 @@ to be used alongside the traditional `m.login.password`. ## Proposal +### No change to `POST /login` +The `/login` API endpoint already supports authentication types beyond just +`m.login.password`. + ### Changes to `POST /register` Instead of sending the user's password as a top-level element of the JSON body, @@ -86,8 +90,6 @@ The proposed approach is to add a new `GET` method for `/register`, similar to what is already done for `/login`. The server responds with a list of the supported authentication types. -`GET /register` - ```json { "auth_types": [ @@ -188,32 +190,7 @@ DELETE /account/authenticator/m.login.webauthn/abcdwxyz ``` -### Changes to `POST /login` - -For `/login`, the top-level elements `type` and `password` in the JSON -body are replaced by an `authenticators` object containing authentication -data for one or more auth types. -For example, with `m.login.password`: - -``` -POST /login -``` - -```json -{ - "identifier": { - "type": "m.id.user", - "user": "cheeky_monkey" - }, - "initial_device_display_name": "Jungle Phone", - "authenticators": { - "m.login.password": { - "password": "ilovebananas" - } - } -} -``` ## Potential issues