Sign-in providers
A player signs in with a device, or with an account of a provider you enable. Open Project settings → Authentication and choose Staging or Production in the header. Each environment holds up to ten connections, including disabled ones. Only the owner changes them; editors and support can view the list and settings.
Add and configure a connection
Section titled “Add and configure a connection”Your connections shows the connections already added, their names, provider types and Enabled or Disabled status, with the count out of ten. The catalog below offers nine provider types. Choose a card to open a panel on the right, enter a connection name and the provider’s parameters, then choose Add connection. New connections are enabled by default. You can add the same provider type several times with different names. At ten connections, delete one before adding another.
Choose Configure on a connection to open its saved settings. Its name and provider type stay fixed; the owner can change parameters and Enabled status. The action menu also enables, disables or deletes the connection. Deletion asks for confirmation. Closing a changed form asks before discarding it.
The panel identifies the provider and environment being configured. A connection belongs to that environment only; switching the project or environment closes its form.
Secrets
Section titled “Secrets”Providers that need a secret let you enter one when adding a connection, or leave it empty to have Rudder generate one. A secret must contain 16–256 bytes. For Facebook, VK ID and Yandex Games, use the secret issued for your app or game by that provider.
A new or replaced secret is shown once after saving; copy it before closing the dialog. Later, only its last four characters are visible. Choose Replace secret to enter or generate a replacement; Keep current secret cancels the replacement. Replacing it requires confirmation: the old secret stops working as soon as the change is saved. Disabling or deleting a connection stops new sign-ins through it; existing player identities remain, and issued tokens keep working until they expire.
The platform verifies the account itself: the game sends what the provider gave it — an ID token, an access token, a code, a signature — and Rudder checks the signature against the keys of the provider, or asks the API of the provider with the secret you stored. Nobody runs a service of their own except with the webhook kind, which exists for the cases nothing else covers. What each provider sends, what the platform checks and the code of both SDKs are in Authentication.
The name is the identity
Section titled “The name is the identity”A connection name contains 1–32 lower-case letters, digits, underscores or hyphens and must be
unique in its environment. device is reserved. The name is the identity the player is signed
in with, so google and yandex are good names and corp-sso works too. Creating a connection
with another name creates a new identity: the players signed in with the old name are not
found by the new one.
A player holds one identity per provider and any number of them together. linkProvider on a
session attaches another one to the player, and unlinkIdentity detaches it; the last identity
of a player cannot be unlinked. A player who signs in with a provider for the first time gets a
new player; that player is the same on every later sign-in.
Device sign-in is always available and cannot be turned off, so a game always has a way in.
What the game calls
Section titled “What the game calls”const session = await Rudder.signIn(key, { provider: 'crazygames', payload: { idToken } });
await session.linkProvider({ provider: 'google', payload: { idToken: googleIdToken } });payload is a JSON object of at most 16 KB and at most 32 top-level keys, forwarded as it is to
the provider check. The fields each kind reads are on its page. The profile options
(nickname, avatar, language, region) work as they do for a device sign-in: a nickname
and an avatar are applied only while the player has none, and the language and the region are
replaced at every sign-in. A nickname and an avatar that the provider itself gives are used
before those.
| Error | Meaning |
|---|---|
401 unauthorized | The provider is missing or off, or it refused the token. |
409 identity_taken | The account is already attached to another player. |
400 invalid_request | The payload is not an object, or is too big. |
503 try_again | The provider could not be reached; the SDK sends the call again. |