GitHub authentication

GitHub authentication lets your users sign in with the GitHub account they already use for developer tools and projects. Once connected, you can offer “Continue with GitHub” in your WeWeb app.

What this integration supports

• Social sign in with GitHub
• Redirect to different pages for success, error, and first-time users

Setup in the GitHub dashboard

1. Go to your GitHub account settings and open Developer settings.
2. Open OAuth Apps and click New OAuth App.
3. Fill in the app details:
   • Homepage URL: your app’s URL (preview or production)
   • Authorization callback URL: the redirect URL GitHub sends users back to after login
4. For the callback URL, use the full URL of the page you select as Success page in WeWeb.
5. Create the app, then copy:
   • Client ID
   • Client Secret

Connect GitHub in WeWeb

1. In the WeWeb editor, go to Data & API → Auth → Integrating providers.
2. Select GitHub and turn on the Enable toggle.
3. Paste your credentials into the fields shown in WeWeb:
   • Client ID
   • Client Secret
4. Click Save.

Test sign in

1. In Interface, add a “Continue with GitHub” button.
2. Create a workflow on click and add Sign in with social provider.
3. Set:
   • Provider: github
   • Success page, Error page, And (optional) New user page
4. Preview your app and complete the GitHub sign-in flow.

To learn how sessions, roles, and protected pages work after sign in, refer to the shared auth docs.

Common pitfalls

Redirect URL mismatch

If GitHub shows a callback or redirect error:

• Make sure the Authorization callback URL in GitHub exactly matches the Success page URL you selected in WeWeb.
• Check you’re using the correct environment (preview vs production).

App shows “not allowed” or missing permissions

If users can’t complete the sign-in flow, confirm you created the correct type of OAuth app and that it’s active in your GitHub settings.

Reference

Settings

Setting in WeWeb	Description	Where to find it in GitHub
Client ID	Identifies your GitHub OAuth app.	Settings → Developer settings → OAuth Apps.
Client Secret	Used to complete the sign-in flow securely.	Same OAuth app page (Generate a new client secret if needed).

FAQs

Which callback URL should I add in GitHub?

Use the full URL of the page you select as Success page in Sign in with social provider (for the environment you’re testing).

Can I use GitHub sign in and email/password together?

Yes. You can enable multiple providers and let users choose how to sign in.