weegloo-service-login-gitlab

Guides GitLab OAuth application registration to obtain clientId and clientSecret for Weegloo ServiceLogin.

1|2|Updated Feb 20, 2026

Search Tags:#authentication #oauth #gitlab #redirect-uri #client-secret #weegloo #service-login

One-click install

npx skills add https://github.com/weeglooapi/weegloo-mcp-plugin --skill weegloo-service-login-gitlab-weeglooapi

Or copy as Structured Prompt for Agent▼

Please help me install this Agent Skill.
Skill: weegloo-service-login-gitlab
Source: https://github.com/weeglooapi/weegloo-mcp-plugin/tree/main/plugins/weegloo/skills/weegloo-service-login-gitlab
Command: npx skills add https://github.com/weeglooapi/weegloo-mcp-plugin --skill weegloo-service-login-gitlab-weeglooapi

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Setting up GitLab as an OAuth 2.0 provider for Weegloo ServiceLogin requires exact console steps, the correct Redirect URI, and the right scope choices; this Skill walks through registering a GitLab application and producing the clientId and clientSecret that ServiceLogin needs. ## Core Features & Use Cases - GitLab Application Registration Walkthrough: Step-by-step instructions for User settings → Applications, including the exact Redirect URI format `https://auth.weegloo.com/v1/spaces/{spaceId}/login/oauth2/code/gitlab`. - Credential Handling Guidance: Explains that GitLab shows the Secret only once, that Application ID maps to clientId and Secret to clientSecret, and how to renew a lost secret. - Scope and Security Rules: Enforces ticking only `read_user` (GitLab refuses to save with no scopes), keeping Confidential enabled, and avoiding `api`/`read_api` to follow least privilege. - Use Case: A developer adding GitLab sign-in to a Weegloo-powered app uses this Skill to instruct the product owner on creating the GitLab OAuth application, then creates the ServiceLogin with the returned credentials, defaultRole, and callbackUrl. ## Quick Start Ask the agent to set up GitLab as the OAuth provider for Weegloo ServiceLogin in your space and walk you through registering the GitLab application.

Frequently Asked Questions about weegloo-service-login-gitlab

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I set up GitLab OAuth login for Weegloo ServiceLogin?▼

Sign in to GitLab, go to User settings → Applications, and add a new application with the Redirect URI https://auth.weegloo.com/v1/spaces/{spaceId}/login/oauth2/code/gitlab. Tick only the read_user scope, save, then copy the Application ID and Secret as the clientId and clientSecret.

What Redirect URI should I register in my GitLab OAuth application?▼

Register https://auth.weegloo.com/v1/spaces/{spaceId}/login/oauth2/code/gitlab with your real spaceId substituted. The /code/ segment is required, and this URI is known before deployment so it can be registered immediately.

Which GitLab OAuth scopes does Weegloo ServiceLogin need?▼

Only read_user is needed; GitLab requires at least one scope to save the application. Weegloo uses it to read the member's email, while api and read_api should stay off to follow least privilege.

What happens if I lose the GitLab application secret?▼

GitLab shows the Secret only once at creation, so copy it immediately. If lost, use Renew secret on the same screen to issue a new one, then update the ServiceLogin with the new clientSecret.

Can I use this GitLab setup guide for Google or GitHub sign-in?▼

No, this Skill applies only when GitLab is the chosen provider. Google, GitHub, Facebook, Kakao, Naver, and LINE each have dedicated provider skills because their console steps differ.