weegloo-service-login-client

Implements Weegloo ServiceLogin OAuth 2.0 sign-in for browser and native apps via wire protocol and SDK.

1|2|Updated Feb 20, 2026
One-click install
npx skills add https://github.com/weeglooapi/weegloo-mcp-plugin --skill weegloo-service-login-client-weeglooapi
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: weegloo-service-login-client
Source: https://github.com/weeglooapi/weegloo-mcp-plugin/tree/main/plugins/weegloo/skills/weegloo-service-login-client
Command: npx skills add https://github.com/weeglooapi/weegloo-mcp-plugin --skill weegloo-service-login-client-weeglooapi

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires weegloo-service-user.

What problem does it solve? Integrating OAuth 2.0 social sign-in (Google, GitHub, Facebook, GitLab, LINE, Kakao, Naver) into a Weegloo product requires knowing the exact auth.weegloo.com endpoints, the token exchange flow, and pitfalls like the entry-URL vs redirect-URI confusion — this Skill provides the complete implementation layer so sign-in works on the first attempt. ## Core Features & Use Cases - OAuth Wire Protocol: Documents the exact HTTP endpoints on auth.weegloo.com for login entry, token exchange, refresh, and logout, usable from any HTTP client. - Browser SDK Integration: Covers the weegloo-service-user npm package with login redirect, callback handling, token storage, auto-refresh, and exchangeToken URL-stripping. - Native App Path: Explains registering deep links in allowedCallbackUrls and driving the flow with redirect_uri plus PKCE for Android and iOS apps. - Use Case: You are building a web app on a Weegloo Space and need "Sign in with GitHub" — this Skill walks you through creating the ServiceLogin, registering the provider redirect URI, and wiring the SDK callback page. ## Quick Start Add Weegloo ServiceLogin sign-in with the appropriate OAuth provider to my browser app using the weegloo-service-user SDK.

Frequently Asked Questions about weegloo-service-login-client

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

FAQPage Schema
How do I add OAuth social login to a Weegloo web app?

Create a ServiceLogin resource with the provider's clientId and clientSecret, then use the weegloo-service-user npm SDK in the browser. Call auth.login() to redirect, and auth.handleCallback() on the callback page to exchange the token.

What is the difference between the login entry URL and the provider redirect URI?

The entry URL is /v1/spaces/{spaceId}/login/oauth2/{provider}, navigated to by the user's browser. The redirect URI is /login/oauth2/code/{provider}, registered in the provider's developer console and called by the provider back to Weegloo.

Can I use the weegloo-service-user SDK in an Android or iOS app?

No, the SDK is browser JavaScript only. Native apps must implement the wire protocol directly with the platform's HTTP client, register a deep link in allowedCallbackUrls, and use PKCE with redirect_uri on the login entry URL.

Why does the OAuth token exchange fail in the browser?

Browsers cannot send a body on GET requests, so the token exchange must use POST with Content-Type: application/json and the exchangeToken in the JSON body. Also strip the exchangeToken from the URL with history.replaceState before the network call.

How do I get the current signed-in user after ServiceLogin?

Call GET https://acma.weegloo.com/v1/me with the ServiceLogin Bearer token. Do not use /v1/spaces/{spaceId}/me — ACMA does not mirror the space-scoped path pattern used by auth.weegloo.com for the identity endpoint.