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

[feat][RFC] HTTP/Websockets Authentication API #34

Open
TsFreddie opened this issue Aug 27, 2021 · 1 comment
Open

[feat][RFC] HTTP/Websockets Authentication API #34

TsFreddie opened this issue Aug 27, 2021 · 1 comment

Comments

@TsFreddie
Copy link
Contributor

We want our own global ban system, but solely relying on a remote command execute system can cause some issues like banlist desync and over populating.

So what if, instead, we make a standard configurable HTTP API for authenticating users when joining.

Joining server might become slower because server need to send request to a http server, but this way we can offload ASN/VPN banning and global ban to a web server.

We are definitely keeping the old ban system for local bans and for hosters who don't want to setup a authentication server.

And we still need the remote command system for banning a players after they have joined.

@TsFreddie TsFreddie changed the title [feat][RFC] HTTP Authenticate API [feat][RFC] HTTP/Websockets Authentication API Aug 28, 2021
@TsFreddie
Copy link
Contributor Author

TsFreddie commented Aug 28, 2021

And we still need the remote command system for banning a players after they have joined.

We can allows servers to connect to a websocket connection that a web service provide to receive new ban infomations.

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