Configuration
To start using Sign in with Google we first need to configure our integration in the platform settings.
Client ID
Client ID can be retrieved from the Google Dev Console. If you don't have an OAuth2 Client ID, you will have to create one.
Start Session
You need to acquire a Google Identity Token to be able to start a Google session, but once you have that, simply follow along to the code snippet below. In the response from LootLocker you will find a refresh token which can be used to refresh the session so that you do not need to do the full sign-in flow each time.
To copy and paste the above example into your editor, look here.
Input
You need to exchange the TriggerGoogleSignIn event for whatever event you want to use to trigger the login flow. Remove the node REPLACE: Google ID Token and replace it with your preferred method of getting the Google Identity Token.
Output
We recommend branching the completed events on the success flag, and if you do this you will probably want to add error handling in case the request fails as well as what (if any) continued actions you want on success. For subsequent calls to different LootLocker methods you will want to create variables from the Player Id and Player Identifier outputs. In the session response when starting an Apple session you also get a refresh token that we will save under the hood. But if you want to use it manually, we provide it for you.
Beyond those three, there is a lot of interesting stuff in the session response, like current xp and level for example.
Example response:
Refresh Session
With Google authentication, you can refresh the session instead of having the player do a full sign-in every time. The request will return a 401 (Unauthorized) if the refresh token has expired, in which case you will need to start a new session.
To copy and paste the above example into your editor, look here.
Input
You need to exchange the TriggerSessionRefresh event for whatever event you want to use to trigger the login flow. The node Refresh Token is the one you saved when starting a session, but it is optional as we save it behind the scenes as well.
Output
We recommend branching the completed events on the success flag, and if you do this you will probably want to add error handling in case the request fails as well as what (if any) continued actions you want on success. For subsequent calls to different LootLocker methods you will want to create variables from the Player Id and Player Identifier outputs. In the session response when starting an Apple session you also get a refresh token that we will save under the hood. But if you want to use it manually, we provide it for you.
Beyond those three, there is a lot of interesting stuff in the session response, like current xp and level for example.
Example response:
Congratulations - you have now started using LootLocker in your game with Sign in with Google! Next up we suggest you look at our feature set, and decide which ones you want to use in your game.
Last updated