How to Integrate AccelByte with Existing User Authentication Systems

Hi everyone, :wave:

I am currently working on a project to seamlessly integrate AccelByte’s robust services with our existing user authentication system. Our platform utilizes a custom-built authentication mechanism, and I’m committed to ensuring a smooth transition for our users as they explore the enhanced features AccelByte offers.

I’m reaching out to the community for guidance and insights on the following key areas:

  • User Data Synchronization: How can we efficiently synchronize user data between our system and AccelByte to minimize disruptions and optimize user experience? Are there recommended best practices or tools to streamline this process?
  • Authentication Flow Integration: What’s the most effective approach to integrate our current login system with AccelByte’s authentication flow? Should we leverage AccelByte’s authentication services directly or explore federation options?
  • Security Best Practices: What specific security measures should we prioritize when integrating our authentication system with AccelByte? Are there common vulnerabilities or pitfalls to be aware of?
  • API Utilization: Could you point me to specific AccelByte APIs that can simplify this integration? Any relevant documentation or code examples would be incredibly helpful.

I also check this: https://community.accelbyte.io/t/custom-attributes-not-being-passed-in-session-informationmendix I am eager to learn from the experiences of others who have successfully navigated a similar integration. Your insights, advice, or recommendations would be invaluable to our team.

Thank you in advance for your time and expertise. :blush:

hello @ash45

Based on your scenario, you may be interested in federating your existing user authentication system with the AGS system using the OpenID Connect (OIDC) protocol. To do so, your current authentication system should be OIDC-compliant beforehand.

Related guide: Set up OIDC as an identity provider | AccelByte Documentation.

Regarding user data synchronization, once login federation with AGS is established, your Game Client can use the AGS user’s access token to leverage our APIs and perform a lazy migration of user data into the AGS system.
However for server-side user data (e.g. player ingame entitlements, coin, etc), a more advanced solution is necessary, such as performing server-to-server (S2S) API calls between your system and the AGS system.

Hope this help.