GitLab authentication

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

What this integration supports

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

Setup in the GitLab dashboard

1. Sign in to GitLab and open your profile settings.
2. Go to Applications (sometimes under Preferences).
3. Create a new application.
4. Add a redirect URL (the URL GitLab sends users back to after login).
   • Use the full URL of the page you select as Success page in WeWeb.
5. Save the application and copy the values GitLab provides:
   • Application ID (Use this as Client ID in WeWeb)
   • Secret (Use this as Client Secret in WeWeb)

Connect GitLab in WeWeb

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

Test sign in

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

Common pitfalls

Redirect URL mismatch

Make sure the redirect URL in GitLab exactly matches the Success page URL you selected in WeWeb (including https:// and any path).

Using the wrong GitLab host

If you use a self-hosted GitLab instance, make sure you created the application in the correct GitLab environment (not on gitlab.com).

Reference

Setting in WeWeb	Description	Where to find it in GitLab
Client ID	Identifies your GitLab application.	Applications page (Application ID).
Client Secret	Used to complete the sign-in flow securely.	Applications page (Secret).

FAQs

Which redirect URL should I add in GitLab?

Use the full URL of the page you select as Success page in Sign in with social provider.