Skip to main content
Authentication & Players

Not translated yet — showing English.

SSO & Auth

SSO & Auth decides which providers players can sign in with. Each provider is a card: you enter the credentials from the provider's developer console, test them, and switch the provider on. Open it from Players → SSO & Auth. The providers and their credentials apply to the whole project, in every environment; only the list of failed and refused sign-ins follows the environment selected in the top bar.

The header counts the enabled providers out of all six cards, including the two that are coming soon.


Providers

ProviderSigns players in withStatus
GoogleA Google account, over OAuth 2.0Available
FacebookA Facebook or Meta account, over OAuth 2.0Available
AppleSign in with Apple. An iOS app that offers any other social sign-in must offer it too, under App Store guideline 4.8.Available
EpicAn Epic Games account, through Epic Online Services. Worth enabling if you ship on the Epic Games Store or target Epic account holders.Available
PlayServ WebhookYour own auth server calls PlayServ: for games that already have their own login.Coming soon
PlayServ Auth TokenThe SDK passes a token you sign on your server: for games that mint their own JWTs.Coming soon

Steam sign-in is supported by the platform and the SDK, but it can't be configured in the Backoffice yet.


Set up a provider

Every provider follows the same path: credentials from the provider's console, the card's Redirect URI back into that console, then Save, Test connection and the toggle. The card shows unsaved changes until you save.

Create an OAuth client in Google Cloud

In the Google Cloud console, open or create a project, go to APIs & Services → Credentials and create an OAuth 2.0 Client ID of type Web application.

Enter the credentials

Expand the Google card and fill in:

FieldWhat to enter
Client IDThe OAuth client's ID.
Client SecretThe OAuth client's secret.
Redirect URIRead-only: generated by PlayServ, copy it in the next step.

Register the Redirect URI

Add the card's Redirect URI to the client's Authorised redirect URIs in Google Cloud and save there.

Save, test and switch on

Click Save, then Test connection, then turn on the toggle.

Get the app credentials from Meta

In Meta for Developers, open or create an app and copy the App ID and App Secret from Settings → Basic.

Enter the credentials

Expand the Facebook card and fill in:

FieldWhat to enter
App IDThe app's numeric ID, 15 to 17 digits.
App SecretThe app secret, 32 hexadecimal characters.
Redirect URIRead-only: generated by PlayServ, copy it in the next step.

Register the Redirect URI

Add the card's Redirect URI to Valid OAuth Redirect URIs under Facebook Login → Settings and save there.

Save, test and switch on

Click Save, then Test connection, then turn on the toggle.

Set up Sign in with Apple

In Apple Developer → Certificates, Identifiers & Profiles, enable Sign in with Apple on your app's identifier and create a Services ID for it.

Create a key

Under Keys, create a key with Sign in with Apple enabled and download its .p8 file. Note the Key ID, and your Team ID from the top-right corner of the portal.

Enter the credentials

Expand the Apple card and fill in:

FieldWhat to enter
Services IDThe Services ID registered under your App ID.
Team IDYour Apple Developer team ID.
Key IDThe ID of the Sign in with Apple key.
Private key (.p8 PEM)The contents of the .p8 file, a P-256 key.
Redirect URIRead-only: generated by PlayServ, copy it in the next step.

Register the Redirect URI

Add the card's Redirect URI to the Return URLs of the Services ID under Sign in with Apple → Configure and save there.

Save, test and switch on

Click Save, then Test connection, then turn on the toggle.

Get the client credentials from Epic

In the Epic Developer Portal, open your product and copy a client's Client ID and Client Secret from Product Settings → Clients, and the Deployment ID you want players to sign in to.

Enter the credentials

Expand the Epic card and fill in:

FieldWhat to enter
Client IDThe Epic Online Services client ID.
Client SecretThe client's secret.
Deployment IDThe deployment to sign players in to. PlayServ works out the product and sandbox from it.
Redirect URIRead-only: generated by PlayServ, copy it in the next step.

Register the Redirect URI

Add the card's Redirect URI to the client's Redirect URL(s) under Product Settings → Clients and save there.

Save, test and switch on

Click Save, then Test connection, then turn on the toggle.

Test connection lists each check as passed, failed or a warning, and the card remembers when it was last tested and how it went. It can also run on unsaved edits, to try credentials before saving them; such a test doesn't change the card's status. The toggle takes effect at once.

Unsaved changes are lost

Edits to a card are only a draft until you click Save. Leaving the page or clicking Cancel throws them away.


Connection status

StatusMeaning
not configuredNothing has been saved yet.
incompleteA required field is missing.
configuredEvery required field is saved, but no test has passed.
verifiedA test passed. Saving new credentials keeps this status, so it doesn't prove the current ones work.

A provider is offered to players when it is switched on and configured or verified. Turning it off removes it from the providers your game is offered.

Enabled isn't the same as verified

The toggle doesn't wait for a test, so a provider can be on with credentials that don't work. Run Test connection before switching a provider on, and again whenever you change its credentials.


Test sign-in end to end

Where the Backoffice offers it, Test sign-in in the tab's header opens a page that signs in through your enabled providers exactly as a game would, without writing any code.

Enter a client key

Paste a client key (pk_…) of the project into Public SDK key. The key carries the project and environment, so the page resolves them by itself.

Client keys are created on Projects, in the project's API keys panel: Create key, type Client. Its secret is shown once, in Save your token; if you didn't save it, create a new key.

Pick a provider

The page lights up a card for every provider that is switched on and configured. Google, Apple and Epic run the full sign-in, consent screen included. Steam takes a session ticket from the Steamworks SDK instead, since it has no browser sign-in. Facebook isn't on the page yet.

Check the result

A successful sign-in shows the player ID and session token PlayServ issued.

Test sign-ins create real players

The page signs in for real: a provider account that has never signed in before becomes a new player in the environment, and shows up in Players.


Failed and refused sign-ins

Recent failed and refused sign-ins at the bottom of the tab lists the project's unsuccessful sign-ins, newest first. Failed means the credential was wrong; refused means PlayServ declined it, for example for a banned device or account. Filter by result, and click a row to open that player. Sign-ins that never reached an account show the device fingerprint instead. A single player's attempts are in their details.


Next steps

Last updated on 16 Oct 2026