Skip to content

GitLab

Members sign in with their GitLab account, in the system browser.

ConsoleGitLab applications
Endpoint groupSocial Login
EmailReturned, but not verified — cannot match an existing account
Signs inIn the browser
  1. Open your GitLab profile’s Applications page.

    On a self-managed GitLab the same page is under your profile settings there.

  2. Add a new application and name it what members should see.

  3. Set the Redirect URI to the address from Memberside → API Keys → Social Login → GitLab, which looks like https://yoursite.com/wp-json/memberside/v1/social/callback/gitlab.

  4. Leave Confidential ticked. The secret stays on your server.

  5. Tick only the read_user scope.

  6. Save, then copy the Application ID and Secret. GitLab shows the secret once.

Why the email cannot match an existing account

Section titled “Why the email cannot match an existing account”

GitLab does not assert that the address it returns has been verified. Memberside therefore refuses to attach a GitLab sign-in to an account that already exists by matching the address.

New members can still register through GitLab. Existing members should sign in first and link GitLab from Social Connects.

Under Memberside → API Keys → Social Login → GitLab:

FieldValue
Client IDThe Application ID
Client secretThe Secret
SymptomCauseFix
“The redirect URI included is not valid”The address does not match the registered oneCopy it again
Sign-in succeeds but no profile comes backThe read_user scope was not tickedTick it and save
A second account is created for an existing memberGitLab’s email is unverified, so matching is refusedHave them sign in first, then link
Self-managed GitLab is refusedThe application was created on gitlab.comCreate it on your own instance