Hi everyone,
I’m currently working on a small web-based video game project where players can create accounts and save their progress online. I’m trying to integrate OneAll for social login (Google/Facebook login), but I’m running into some confusion with how the authentication flow should be handled inside a game environment.
Specifically, I want to know the best way to securely link a player’s in-game profile with their OneAll social profile without breaking session handling or causing duplicate accounts when users log in from different devices.
Is there a recommended approach or example setup for handling user identity mapping in a game backend using OneAll APIs? Also, how do others typically manage session persistence for logged-in players in similar use cases?
Any guidance or best practices would be really appreciated.
Please sign in to your OneAll account to ask a new question or to contribute to the discussions.
Please click on the link below to connect to the forum with your OneAll account.