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

Accomodate OIDC authentication #1258

Open
ShadowJonathan opened this issue Aug 14, 2022 · 3 comments
Open

Accomodate OIDC authentication #1258

ShadowJonathan opened this issue Aug 14, 2022 · 3 comments
Labels
effort/hard type/msc issues relating to implementing or updating ruma from MSCs type/refactor

Comments

@ShadowJonathan
Copy link
Member

Background and Context

With areweoidcyet.com, the Matrix Foundation has (imo) displayed enough commitment to the pushing ahead of the likes of MSC3861 (and related MSCs)

For Ruma, this effectively means a deprecation of the old UIA and access_token (or not? unsure) method of authenticating users, or at the very least, that we support the new method for both server(s) and clients.

This is needed for conduit to support OIDC (if it ever will, with its scope goals), but most importantly, this'll be needed for rust-sdk, which is, or is poised to, downstream to a lot of important projects for element.io.


This issue is meant to track and discuss the large-scale implementation of OIDC in Ruma.

Related issues:

  • (TBD)
@ShadowJonathan ShadowJonathan added effort/hard help wanted type/refactor type/msc issues relating to implementing or updating ruma from MSCs labels Aug 14, 2022
@ShadowJonathan ShadowJonathan changed the title Accomodate OIDC Accomodate OIDC authentication Aug 14, 2022
@zecakeh
Copy link
Contributor

zecakeh commented Aug 14, 2022

I'm not sure there's much more to do in Ruma (except for the deprecations when the time comes).

I believe work on OIDC should be centralised in the matrix-authentication-service project as long as it doesn't concern directly the Matrix side. It's written in Rust and split into several crates to separate concerns.

I'm currently involved in creating a client library there that is needed by the project to interact with other OIDC providers and that we also plan to use for the SDK.

Ultimately it'll probably also support the methods required by servers to interact with it, although currently there doesn't seem to be MSCs for how homeservers are supposed to interact with the OIDC provider.

@erlend-sh
Copy link

OIDC login has landed in matrix-rust-sdk: matrix-org/matrix-rust-sdk#859

A PR (MR) for OIDC support in Conduit is pending: https://gitlab.com/famedly/conduit/-/merge_requests/80

@avdb13
Copy link
Contributor

avdb13 commented Mar 28, 2024

OIDC support is nearly complete in Conduit (https://gitlab.com/famedly/conduit/-/merge_requests/587).
Problem is the endpoints aren't stable yet, Ruma doesn't need any changes theoretically speaking unless we want it to play more nicely with the ruma_route macro. Will update on this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
effort/hard type/msc issues relating to implementing or updating ruma from MSCs type/refactor
Development

No branches or pull requests

5 participants