Gate server access #75

New issue

Open

opened 2026-03-04 12:47:40 -08:00 by puregarlic · 0 comments

puregarlic commented

2026-03-04 12:47:40 -08:00

Owner

Create a users table for the server, responsible for tracking the DIDs of authorized users
Add a SERVER_OWNER_DID environment variable, set to the DID of the root admin for the server. At first launch, this should result in the user's DID automatically getting inserted into the users table. For subsequent launches, similar to the default channel, we should check for the number of users and skip insertion as necessary
Add a users gRPC service for managing server users and permissions. The main actions to support are adding and removing users; user permissions are in the scope of #12 for a later time
Add a manager to the client for interacting with the auth service
Add a page to the client for adding and removing users

Even assuming the completion of #69, any user can access any microclimate server if they have a valid Atmosphere account. Since microclimate is being built for private communities, we will need to restrict access to an allowlist. - Create a `users` table for the server, responsible for tracking the DIDs of authorized users - Add a `SERVER_OWNER_DID` environment variable, set to the DID of the root admin for the server. At first launch, this should result in the user's DID automatically getting inserted into the `users` table. For subsequent launches, similar to the default channel, we should check for the number of users and skip insertion as necessary - Add a `users` gRPC service for managing server users and permissions. The main actions to support are adding and removing users; user permissions are in the scope of #12 for a later time - Add a manager to the client for interacting with the auth service - Add a page to the client for adding and removing users