Skip to content

Authentication

A player reaches the game with a session: a player id and an access token that lives 24 hours.

  • A device — the client makes an id and keeps it locally. No provider and no account: what a game without sign-in uses, and the player can attach an account to it later.
  • An account of a provider — the game gets a token from Google, Apple, Facebook, CrazyGames, Yandex, VK or any OpenID Connect provider, and the platform verifies it. Each environment holds up to ten connections.
  • A webhook of yours — the platform asks your own sign-in service who the client is.

The call is the same for every provider — Session.signIn of @rudder/sdk, RudderSdk.Session.SignInAsync in C# — and it is described once in Client SDK. What differs is the payload the game sends and what the platform checks.

ProviderThe game sendsNotes
GoogleidTokenID token of Google Identity Services
AppleidTokenidentity token of the Apple credential
FacebookaccessTokenasked about through the Graph API
CrazyGamesidTokenuser token of their SDK; crazygames.com only
Yandex IDtokenOAuth token, checked asking login.yandex.ru
Yandex GamessignatureHMAC of the player, inside the Yandex Games page
VK IDcode, deviceIdthe platform exchanges the code itself
OpenID ConnectidTokenany issuer with a discovery document
Custom sign-inpayloadposted to your URL and signed

A player holds one identity per provider and any number of them at once: linkProvider attaches another to the session of a player, unlinkIdentity detaches it, and the last identity cannot be detached.

The connections are made on the Authentication screen of the Dashboard, one list per environment — see Sign-in providers. Every provider answers the errors listed in Errors; each page names the ones particular to it.