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

Refactor concept of "AuthProviders" #152

Open
fnwbr opened this issue Mar 12, 2024 · 0 comments
Open

Refactor concept of "AuthProviders" #152

fnwbr opened this issue Mar 12, 2024 · 0 comments

Comments

@fnwbr
Copy link
Member

fnwbr commented Mar 12, 2024

What used to be "authentication providers" are now rather "application" or "service" providers.
Initially we had assumed that every page or service would have their own authentication layer, which was true in case case of Etherpads/MyPads and Spacedeck.

Now with ditching Spacedeck in favor of tldraw one of those services is gone.

Right now I'm not sure what a better solution would look like; but something along the lines of:

  1. Matrix is the primary authentication layer and major entry point
  2. We have "apps", "services" or "applications" such as etherpad, tldraw or something else.
    2.1. Each of those can provide an additional authentication layer, like in the case of Etherpad specifying MyPads
  3. Generally each "application" stores their respective data in a sub-space of the "Applications" Matrix space
  4. Each "application" can provide a custom path for routing / custom name for whitelabeling (e.g. calling the tldraw app /draw or the etherpad app /note)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant