Open S7evinK opened 1 year ago
The login redirect endpoint could very easily be supported given dendeite does not support multiple identiy providers:
This would behave identically to the existing endpoint without the last argument except would allow the server to forward the user directly to the correct IdP.
Afaik, we could alias the endpoint and just ignore the idp suffix until different auth providers are actually implemented.
A list of things to actually announce support for 1.1 (while we already do) While this is about getting actual 1.1 support, it make sense to check https://spec.matrix.org/latest/
Complete changelog v1.1
Client-Server API
New Endpoints
/room_keys/*
) endpoints as per MSC1219.POST /keys/device_signing/upload
andPOST /keys/signatures/upload
as per MSC1756./knock
endpoint as per MSC2403./login/sso/redirect/{idpId}
as per MSC2858.Removed Endpoints
m.login.oauth2
andm.login.token
user-interactive authentication mechanisms as per MSC2610 and MSC2611.m.login.password
right nowBackwards Compatible Changes
device_id
parameter to login fallback as per MSC2604.reason
on all membership events and related endpoints as per MSC2367.M_NOT_FOUND
error to push rule endpoints as per MSC2663.M_NOT_FOUND
reason
andscore
parameters optional in the content reporting API as per MSC2414./report
at all - Spec v1.8device_id
to/account/whoami
response as per MSC2033.Server-Server API
New Endpoints
/make_knock
and/send_knock
endpoints as per MSC2403.Backwards Compatible Changes
GET /user/keys
andGET /user/devices/{userId}
,m.device_list_update
EDU, and a newm.signing_key_update
EDU as per MSC1756.