Sign-in methods
Purpose
This tab is where you manage which providers players can sign in with in the selected environment. The provider managed from the panel today is Google; guest sign-in and email sign-in are not set here. The page also has the environment’s session policy (single active session). Each provider’s detail page has its status, scopes, client information and safe extra information.
When to use
- When turning on Google sign-in for the first time (to enter the client ID, secret and redirect base).
- To temporarily turn Google sign-in off or turn it back on.
- If you want a player’s old sessions to close on their new sign-in.
Step by step
Configure Google sign-in
- Choose the environment at the top of the tab and press Detay (Detail) on the Google row in the list.
- On the OAuth istemci bilgisi (OAuth client information) card press OAuth bilgilerini düzenle (Edit OAuth information). Only a super admin sees the button.
- Enter the client ID, the client secret and the redirect base.
- Write your reason and the 6-digit code from your authenticator app and press Kaydet (Save).
- In the Google Cloud console, register as the Authorized redirect URI your redirect base with
/googleadded at the end. - If the provider is not Etkin (Enabled), press Etkinleştir (Enable) on the detail page.
Warning
The client secret is write-only. After saving it never appears in the panel again; the card shows only a “configured” status and a short fingerprint. If you lose it, get a new one from Google and enter it again.
Single active session
- Turn the Tek aktif oturum (Single active session) switch on the Giriş ayarları (Sign-in settings) card on or off. Only admins with sign-in method write permission can change the switch.
- Write your reason in the window that opens and confirm.
The line under the card shows the value’s source: environment setting or server default.
Remove information entered from the panel
For Google information entered from the panel, a Kaldır (Remove) button appears on the detail page. You confirm by typing the provider’s ID and enter your reason and verification code. If the server has a default value, the environment returns to it; if not, the provider becomes unconfigured in this environment.
Fields and options
| Field | Required | Description |
|---|---|---|
| Single active session | No | A switch per environment; does not touch open sessions |
| Client ID | Yes | At most 256 characters, visible characters without spaces |
| Client secret | Yes | At least 8, at most 1024 characters; write-only |
| Redirect base | Yes in live | Starts with https; contains no query, fragment or user info |
| Action reason | Yes | 8-500 characters |
| Verification code | Yes | The current 6-digit code |
| Confirmation text (removal) | Yes | The provider ID exactly |
| Running state enabled (provider settings) | No | Turns the provider on or off |
| Safe extra information (JSON) | No | Field names that contain secrets are rejected |
Common situations
| Situation | What to do |
|---|---|
The Google button does not appear in the game, or the start returns 403 | Google is not configured or is off in this environment. Enter the information and enable the provider. |
| Google says “redirect_uri_mismatch” | The address you registered in the Google Cloud console must be exactly the same as the redirect base + /google. |
| The “edit information” button is missing | Only a super admin can write client information. |
| “Kaydet” gives a verification code error | A recovery code is not accepted; enter the current 6-digit code from your authenticator app. The code is cleared after each attempt. |
| Server default appears as the source | The information comes from the server setting. A value you enter from the panel overrides it in this environment. |
| A player cannot stay signed in on two devices at the same time | Single active session is on. If you turn it off, players can stay signed in on more than one device at the same time. |