How to Set Up Social Login with Google for XFile Ultra
Members can sign in or register with their Google account. You create an OAuth 2.0 Web client in Google Cloud, register XFile Ultra’s callback URL, then paste the Client ID and Client secret into Mods → Social.
Before you start
1. Social Login is a Premium plugin. If the Social section shows a lock / “Premium plugin required”, buy Social Login on xfileultra.com, then refresh the license under Settings → Main → Site identity.
2. Turn on the master Social login switch (toggle.mrc) in Admin → Settings → Mods → Social.
3. Copy the read-only Redirect URI shown for that provider — you will paste it into the provider console exactly (https, host, path; no extra slash).
Password sign-in stays available when social login is on.
Where to find it in XFile Ultra
Admin → Settings → Mods → Social
1. Turn Social login on
2. Provider dropdown → Google
3. Turn Google social login on
4. Paste Client ID and Client secret
5. Copy the shown Redirect URI into Google Cloud (Step 1)
6. Save settings
7. Open /login or /register in a private window and click Google
Fields in XFile Ultra
| Field in admin | Setting key | From Google |
|---|---|---|
| Google social login | toggle.social_google |
Enable/disable this provider |
| Client ID | google_app_id |
OAuth 2.0 Client ID |
| Client secret | google_app_secret |
OAuth client secret |
| Redirect URI | (read-only) | Paste into Google as Authorized redirect URI |
Leave the secret blank on later saves to keep the stored value.
Redirect URI shape:
https://YOUR-DOMAIN/api/auth/oauth/google/callbackScopes used by the product: openid email profile.
Step 1 — Create the OAuth client in Google Cloud
1. Open Google Cloud Console → Credentials
2. Select or create a project
3. If prompted, configure the OAuth consent screen first (see Step 2)
4. Create credentials → OAuth client ID
5. Application type: Web application
6. Name: example XFile Ultra — example.com
7. Under Authorized redirect URIs, click Add URI and paste the Redirect URI from XFile Ultra exactly
8. Create the client
9. Copy Client ID and Client secret
Optional but useful: under Authorized JavaScript origins, add https://YOUR-DOMAIN (no path).
Official overview: Google Identity / OAuth 2.0.
Step 2 — OAuth consent screen
In APIs & Services → OAuth consent screen:
1. Choose External (unless you only use Google Workspace Internal)
2. Fill app name, support email, and developer contact
3. While the app is in Testing, only listed test users can complete Google sign-in
4. Add yourself (and staff) as test users before going public
5. When ready for everyone, publish / verify per Google’s rules (unverified apps show a warning screen)
You do not need a separate Google reCAPTCHA key for social login — that is under Captcha & abuse.
Step 3 — Paste into XFile Ultra and test
1. Admin → Settings → Mods → Social → Provider Google
2. Paste Client ID + Client secret
3. Ensure Social login (master) and Google social login are on
4. Save settings
5. Private window → /login → Google → finish consent → land signed in (or linked)
Common problems
redirect_uri_mismatch
The URI in Google Cloud does not match the admin Redirect URI character-for-character (http vs https, www vs apex, trailing slash, wrong path). Fix Google’s list, wait a minute, retry.
Access blocked / app not verified
Consent screen still in Testing and the Google account is not a test user — or the app needs verification for production use.
Google button missing
Master Social login off, Google social login off, missing Client ID/secret, or Social Login plugin not licensed.
Wrong Redirect URI shown in admin
Set the public site URL correctly (PUBLIC_APP_URL / site origin). The printed callback uses that origin.
Secret blank after save
Normal. Leave empty to keep the stored secret.