In my scenario, I have an existing user base, maintained by a website. Thus, I would like the users to use their existing login credentials (email, username, password). The application will be a desktop app, not a web app. Pretty much all of the documentation around authentication assumes the scenario is a web app.
Here's how I see it working:
- Client app prompts for username and password.
- Client app makes a web request to my site, passing along the user info.
- Website checks the login info against the database of users.
- If the user is authorized, the site generates an authorization hash.
- Client app reads the hash from the request response.
- Client app uses PlayerIO.Connect, passing along the game ID, connection ID, username, and hash.
- Client app should now have a PlayerIO Client.
Is this the appropriate technique?
If so, I have a few further questions. With custom authentication, do the players still have access to PayVault and the other player-specific features that would normally be available to Simple users? How are the custom-authenticated users stored in the PlayerIO backend? Are they listed under the QuickConnect admin page like other users?