Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Declare support for Matrix 1.1 #3216

Open
10 of 13 tasks
S7evinK opened this issue Sep 28, 2023 · 2 comments
Open
10 of 13 tasks

Declare support for Matrix 1.1 #3216

S7evinK opened this issue Sep 28, 2023 · 2 comments
Labels
help wanted More difficult than good-first-issue but not impossible! spec-compliance Fix something that doesn't comply with the specs

Comments

@S7evinK
Copy link
Contributor

S7evinK commented Sep 28, 2023

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

  • Add key backup (/room_keys/*) endpoints as per MSC1219.
  • Add POST /keys/device_signing/upload and POST /keys/signatures/upload as per MSC1756.
  • Add /knock endpoint as per MSC2403.
  • Add /login/sso/redirect/{idpId} as per MSC2858.

Removed Endpoints

  • Remove unimplemented m.login.oauth2 and m.login.token user-interactive authentication mechanisms as per MSC2610 and MSC2611.
    • I think we never added this, also we only support m.login.password right now

Backwards Compatible Changes

  • Add a device_id parameter to login fallback as per MSC2604.
  • Added support for reason on all membership events and related endpoints as per MSC2367.
  • Add a 404 M_NOT_FOUND error to push rule endpoints as per MSC2663.
    • Looks like we already 404 with M_NOT_FOUND
  • Make reason and score parameters optional in the content reporting API as per MSC2414.
  • Allow guests to get the list of members for a room as per MSC2689.
  • Add device_id to /account/whoami response as per MSC2033.

Server-Server API

New Endpoints

  • Add /make_knock and /send_knock endpoints as per MSC2403.

Backwards Compatible Changes

  • Add cross-signing information to GET /user/keys and GET /user/devices/{userId}, m.device_list_update EDU, and a new m.signing_key_update EDU as per MSC1756.
@S7evinK S7evinK added spec-compliance Fix something that doesn't comply with the specs help wanted More difficult than good-first-issue but not impossible! labels Sep 28, 2023
@spaetz
Copy link
Contributor

spaetz commented Jan 17, 2024

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.

@spaetz
Copy link
Contributor

spaetz commented Jan 17, 2024

Knocking is #3095

S7evinK added a commit that referenced this issue Jan 17, 2024
Part of #3216

The files are basically copied from Synapse, with minor changes to the
called endpoints. We never seem to have had the
`/_matrix/static/client/login/` endpoint, this adds it.
S7evinK added a commit that referenced this issue Mar 21, 2024
Part of #3216 and #3226 

There will be a follow up PR which is going to add the same admin
endpoints Synapse has, so existing tools also work for Dendrite.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
help wanted More difficult than good-first-issue but not impossible! spec-compliance Fix something that doesn't comply with the specs
Projects
None yet
Development

No branches or pull requests

2 participants