Matrix-doc Alternatives

Similar projects and alternatives to matrix-doc

matrix-doc

71 749 9.5 HTML matrix-doc VS matrix-doc

Discontinued Proposals for changes to the matrix specification [Moved to: https://github.com/matrix-org/matrix-spec-proposals]
signin-with-matrix

7 212 0.0 Svelte matrix-doc VS signin-with-matrix

Federated sign-in component for your web app (using Matrix)
WorkOS

workos.com sponsored

The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
matrix-oauth

1 24 0.0 TypeScript matrix-doc VS matrix-oauth

Discontinued An OAuth 2.0 server for Matrix accounts

NOTE: The number of mentions on this list indicates mentions on common posts plus user suggested alternatives. Hence, a higher number means a better matrix-doc alternative or higher similarity.

Suggest an alternative to matrix-doc

matrix-doc reviews and mentions

Posts with mentions or reviews of matrix-doc. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2021-11-16.

MSC2964: Matrix Profile for OAuth 2.0
1 project | news.ycombinator.com | 16 Nov 2021
Sign in with Matrix
6 projects | news.ycombinator.com | 16 Nov 2021

Speaking as project lead for Matrix, while we're always happy to see new projects building on Matrix, we share the concern that users shouldn't be encouraged to enter their Matrix username & password into arbitrary webapps which may or may not be trusted. To be clear: Sign in with Matrix is an independent project from a community member which isn't associated or endorsed by the Matrix core team.
The direction we're headed in the Matrix spec core team is instead towards replacing Matrix's current auth mechanisms with normal Open ID Connect (rather than wrapping our own OIDC-like thing, as we do today) - as per https://github.com/sandhose/matrix-doc/blob/msc/sandhose/oau.... The common login flow would then be for users to be authed by their server using a trusted OIDC identity provider, rather than ever trusting arbitrary clients with their credentials.
This is not finalised yet, as we still want to find ways to support folks authing on known trusted clients without having to embed a web browser - and we don't want to design out cryptographic login (e.g. OPAQUE style auth mechanisms) in future.