Master server design

[Ali_RS]

@jayfella

• User creates an account. They are now allowed to use your game, either as a player or server owner.
• User decides to set up a gameserver.
• User requests to register a new gameserver.
• Server responds by giving the user an oauth token (per gameserver. A user can have 10 servers if they want and each server will have a unique oauth token). You can restrict the amount they can have if you want.
• This token has permission to CRUD a single gameserver data and nothing else.
• User puts that oauth token in their gameserver settings.
• Users new gameserver starts. It sends data to the server with oauth token.
• Server checks if the oauth token is valid.
• Server responds OK with the CRUD request if the oauth token is valid.

So far so clear

What about when some client wants to connect to the game server.

Suppose client has already got the ip:port of the game server from the master server and now wants to make a connection to game server.

Should I also give the client a temporary access token to use when connecting a game server? So the game server can also safely authenticate who is being connected, either doing itself by using the shared public-key or by asking from the master server.