Identity Overview¶
Beamable provides a robust identity solution that integrates with third-party providers, supporting multiple authentication methods to suit different game designs.
Authentication is often tricky and has more edge cases than one normally thinks about, you have to factor in what happens when errors occur and how to handle those errors. Below is a diagram of authentication flow that exposes how you can potentially handle these types of scenarios.
Find the authentication type that best suits your game below and learn how easy it is to integrate into your game.
Login Functions¶
The aspects at the core of Identity in Beamable are the RecoverAccount functions, often called Login functions. These are used throughout all the various sign-in methods. RecoverAccountWithEmail() is used for email and password verification, and RecoverAccountWithThirdParty() is used for third-party authentication providers.
Beamable API Access
The AuthService can be accessed via BeamContext. For more information on how to access services, see the documentation on the Player-Centric API.
1 2 | |
Both of these methods work similarly, returning a PlayerRecoveryOperation. The PlayerRecoveryOperation structure can be used to inspect the account that the user is trying to recover if the correct credentials were supplied. If incorrect credentials were given, the PlayerRecoveryOperation will contain an error, and its isSuccess field will be false.
However, assuming that the credentials are correct, then the PlayerRecoveryOperation.SwitchToAccount() function can be invoked to save the account's access token to the user's device. The next time the user starts the app, the game can check if a token exists for that user, and skip the manual sign-in process (performing a "silent" login).
More info on the various uses for Login can be found on the individual sign in method pages.
Features¶
| Feature | Details |
|---|---|
| Frictionless Authentication | Frictionless authentication is by far the easiest to implement in your game. However, it is very device specific and thus should not be the only method used if you are going to want cross-platform support. |
| Username / Password | Authenticate with a Beamable Username & Password. This method allows users to also create cross platform authentication without integrating social features of other platforms. |
| HTML Sign-In | Create web-based login pages that handle Beamable authentication and account administration. This approach allows you to build custom HTML/JavaScript login forms that can be hosted on websites for browser-based authentication flows. |
| Facebook Authentication | Provide cross platform support in your game by enabling Facebook integration. Here you will find all the info you need to do an integration between Beamable & Facebook for authentication. |
| Google Sign-In | Google's Sign-In manages the OAuth 2.0 flow and token lifecycle, simplifying your integration with Google APIs. A user always has the option to revoke access to an application at any time. |
| Google Play Game Services | Integrate Google Play Games Services (GPGS) for Android authentication with Beamable. This allows users to sign in using their Google Play Games account, enabling seamless cross-device authentication for Android games with GPGS integration. |
| Apple Sign-In | Apple's Sign-In makes it easy for users to sign in to your apps and websites using their Apple ID. Instead of filling out forms, verifying email addresses, and choosing new passwords, they can use Sign in with Apple to set up an account and start using your app right away. All accounts are protected with two-factor authentication for superior security, and Apple will not track users' activity in your app or website. |
| Steam Integration | Valve's Steamworks is a set of tools and services that help game developers and publishers build their games and get the most out of distributing on Steam. This integration allows you to integrate Steam Authentication with Beamable. |