Authentication Servers #103
Replies: 9 comments 23 replies
-
Ideally I would do it so that each instance can only connect to one other authentication server. |
Beta Was this translation helpful? Give feedback.
-
|
Another thing to consider is OAuth2 (Sign-In via Google, etc) Self-hosted servers could, maybe even by default, offer "Sign-In with revolt.chat Account" |
Beta Was this translation helpful? Give feedback.
-
|
maybe rename this to |
Beta Was this translation helpful? Give feedback.
-
|
Hello, |
Beta Was this translation helpful? Give feedback.
-
|
I also need Authentication Server support for my self-hosted instance. Specifically I want to use Authentik. I hope it gets implemented at some point. |
Beta Was this translation helpful? Give feedback.
-
|
I second using the official Revolt server as an Oauth provider for self-hosted instances. |
Beta Was this translation helpful? Give feedback.
-
|
That is a good idea for now, but in the long term, I think Federation would be the best solution to keep centralization low. There's also the emerging Polyproto protocol, which is modeled after Discord and could be implemented instead of ActivityPub or Matrix. See @erlend-sh's reply to another post for more details about this and federation in general. |
Beta Was this translation helpful? Give feedback.
-
|
SSO is a must for such product |
Beta Was this translation helpful? Give feedback.
-
|
I disagree. Let's say one day the authentification server closes. What do you do ? How do you get your things back ? Having multiple accounts is the right way to go, so even if one host fails, or if hosts can't communicate between them anymore, you can still access your data everywhere. Centralisation should be avoided. However, it is true that creating an account for every host is exhausting. A tool to automate account generation on a new host is not a bad idea. Like you could link a vault to your session, and the newly automatedly created account would then be added to the vault like KeePassXC or Bitwarden. That way, you don't have any hassle creating a new account, a new password etc, but you keep access to them. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Issue
If you join five different Revolt (self hosted) instances you have to create five different accounts for each instance.
This can get annoying because you have to create a account even if you are planning to join that instance temporarily.
Also you have to trust the hoster that he did not tamper with the service in order to sniff your entered credentials.
Possible Solution
Create a publicly hosted authentication server where people can register.
Additionally you can host your own authentication server.
Once you join a self hosted instace you can choose a authentication server using a drop-down menu.
If you choose to log in using the public authentication server you will be redirected to something like auth.revolt.chat and once you logged in you will be returned to the self hosted instance.
The available/allowed authentication servers should be configurable (e.g. .env).
Maybe other login providers (oauth2) could be included so you can log in with steam, google etc..
Problems
There are probably many issues with this suggestion and my suggested solution is probably not the best.
What happens if two people join a self hosted instace with the same name from two different authentication servers?
Feel free to comment how you would implement such an authentication system
Beta Was this translation helpful? Give feedback.
All reactions