Provider Setup Guide

Go to console.cloud.google.com and sign in with your Google account.

Click the project dropdown at the top left and either select an existing project or click New Project. Give it a name that identifies your game (e.g. My Game — Auth).

Navigate to APIs & Services → OAuth consent screen. If you haven't done this before, you'll need to set it up first.

• Choose External as the user type (unless you have Google Workspace).
• Fill in the app name, support email, and developer contact email.
• On the Scopes step, add openid, email, and profile.
• You don't need to add test users unless the app is in testing mode.
• Save and continue through the remaining steps.

Navigate to APIs & Services → Credentials. Click + Create Credentials → OAuth client ID.

• Application type: Web application
• Name: anything descriptive (e.g. Oathwall)

Under Authorized redirect URIs, click Add URI and enter the Oathwall callback URL:

https://sso.oathwall.com/auth/callback

Click Create. A dialog will show your Client ID and Client Secret. Copy both — you'll paste them into the Oathwall dashboard.

Go to developers.facebook.com and log in with a Facebook account that has developer access.

Click My Apps → Create App. When prompted for an app type, choose Consumer (for games targeting regular users) or Business if you're operating under a business portfolio.

• Fill in the display name for your app (shown to users during login).
• Optionally link a Business Account.
• Click Create App.

On the app dashboard, find the Add a product section and click Set up next to Facebook Login. Choose Web as the platform.

When it asks for a site URL, you can enter your game's website or just skip this step — the important configuration is done in the next step.

Go to Facebook Login → Settings in the left sidebar. Under Valid OAuth Redirect URIs, add:

https://sso.oathwall.com/auth/callback

Click Save Changes.

Go to App Review → Permissions and Features. Make sure email and public_profile are enabled — these are available by default and don't require review.

Navigate to Settings → Basic. At the top you'll see your App ID. Click Show next to App Secret, confirm your password, and copy both values.

Go to developer.apple.com/account and sign in. Note your Team ID in the top-right corner — you'll need it later.

Go to Certificates, Identifiers & Profiles → Identifiers. Click + and select App IDs.

• Type: App
• Description: your game name
• Bundle ID: your reverse-domain identifier (e.g. com.yourstudio.yourgame)
• Scroll down and check Sign In with Apple under Capabilities.
• Click Continue → Register.

Back on Identifiers, click + and this time select Services IDs.

• Description: e.g. My Game Auth Service
• Identifier: a reverse-domain string that is different from your App ID — this becomes your Client ID in Oathwall. Example: com.yourstudio.yourgame.auth
• Click Continue → Register.

Click on the Services ID you just created. Check Sign In with Apple and click Configure.

• Primary App ID: select the App ID you created in step 2.
• Website URLs → Return URLs: add the Oathwall callback:

https://sso.oathwall.com/auth/callback

• Click Next → Done → Continue → Save.

Go to Keys in the sidebar, click +.

• Give the key a name (e.g. Oathwall Key).
• Check Sign In with Apple.
• Click Configure and select your Primary App ID.
• Click Save → Continue → Register.

After registering, you'll see a Download button. Download the .p8 file now — Apple will not let you download it again after you leave this page.

Note the Key ID shown on this page (also visible later in the Keys list).

You now have everything you need:

• Client ID — the Services ID identifier
• Team ID — top-right of the Developer portal
• Key ID — shown on the Keys page
• Private Key — the contents of the .p8 file (open it in a text editor and copy everything including the headers)

You need a game registered on Steamworks. Players authenticate via their Steam account, so they need to own or have access to your game (you can set it to free-to-play or use playtest builds during development).

Go to steamcommunity.com/dev/apikey.

• Sign in with the Steam account that owns your game.
• Enter a domain name for your application (e.g. oathwall.com or your game's domain).
• Agree to the Steam Web API Terms of Use.
• Click Register.

Your Steam Web API Key will be displayed on the same page. Copy it — this is what you'll paste into Oathwall as the Client Secret.

Your Steamworks App ID is available in the Steamworks partner portal. You don't need it for Oathwall configuration, but it's useful to have handy when debugging player login issues.

Go to discord.com/developers/applications and log in with your Discord account.

Click New Application, give it a name (e.g. My Game Auth), and click Create. The name is shown to players on the OAuth consent screen.

In the left sidebar, go to OAuth2. Under Redirects, click Add Redirect and enter:

https://sso.oathwall.com/auth/callback

Click Save Changes.

Still on the OAuth2 page, you'll see your Client ID near the top. Click Reset Secret to generate and reveal your Client Secret. Copy both values.

Go to github.com/settings/developers and select OAuth Apps in the left sidebar.

Click New OAuth App and fill in the details:

• Application name: your game's name (shown to players)
• Homepage URL: your game's website
• Authorization callback URL:

https://sso.oathwall.com/auth/callback

Click Register application.

On the app page you'll see your Client ID. Click Generate a new client secret. Copy the secret immediately — it won't be shown again.

Go to dev.epicgames.com/portal and sign in. If you don't have an organization yet, create one first.

Select an existing product (your game) or create a new one. Inside the product, navigate to Epic Account Services.

Under Clients, click Add new client.

• Give it a descriptive name (e.g. Oathwall).
• Set the client policy to Confidential (server-side secret).

In the client settings, add the Oathwall callback URL under Redirect URIs:

https://sso.oathwall.com/auth/callback

Save the client. Your Client ID and Client Secret are shown in the client detail page. Copy both to the Oathwall dashboard.

Go to dev.twitch.tv/console and log in with your Twitch account.

Click Register Your Application and fill in the form:

• Name: your app name (shown to users during login)
• OAuth Redirect URLs: add the Oathwall callback:

https://sso.oathwall.com/auth/callback

• Category: choose Game Integration or Other.
• Click Create.

Click Manage on your new application. You'll see the Client ID directly. Click New Secret to generate the Client Secret, then copy both values.

Go to developer.twitter.com/en/portal/dashboard and sign in. Create a developer account if you don't have one.

Click Add App (or create a new project first, then add an app inside it). Give the app a name.

In your app settings, go to User authentication settings and click Set up.

• Enable OAuth 2.0.
• App type: Web App, Automated App or Bot.
• Callback URI: add the Oathwall callback:

https://sso.oathwall.com/auth/callback

• Website URL: your game or studio website.
• Click Save.

After saving, Twitter will display your Client ID and Client Secret. Copy them now — the secret won't be shown again.

Go to the Azure App Registrations page and sign in with your Microsoft account.

Click New registration and fill in the details:

• Name: your game or studio name
• Supported account types: choose Accounts in any organizational directory and personal Microsoft accounts to support all players.
• Redirect URI: select Web and enter:

https://sso.oathwall.com/auth/callback

Click Register.

On the app overview page, copy the Application (client) ID — this is your Client ID in Oathwall.

In the left sidebar, go to Certificates & secrets. Under Client secrets, click New client secret.

• Add a description (e.g. Oathwall) and choose an expiry period.
• Click Add.
• Copy the Value immediately — it's hidden after you leave the page.

Sign in to the Oathwall dashboard and navigate to Apps in the sidebar. Click on the app you want to configure.

Inside your app's detail page, click the Providers tab. You'll see all supported providers listed. Unconfigured providers appear greyed out.

Find the provider you want to enable and click Configure. A configuration panel will appear with the fields specific to that provider.

Paste the values you collected from the provider's developer console:

Click Save. The provider will appear as Enabled in the list. You can disable it at any time without deleting the credentials.