What problem does it solve? Setting up LINE as an OAuth provider for Weegloo ServiceLogin requires navigating the LINE Developers console correctly, registering the exact Weegloo callback URL, and avoiding pitfalls like conflating LINE's "Provider" concept with Weegloo's provider value or missing the separate email-permission application that blocks sign-ins. ## Core Features & Use Cases - LINE Login channel walkthrough: Guides the user through creating a LINE Login channel in the LINE Developers console and obtaining the Channel ID (clientId) and Channel secret (clientSecret). - Callback URL registration: Provides the exact deploy-independent callback URL (https://auth.weegloo.com/v1/spaces/{spaceId}/login/oauth2/code/line) to register before building. - Email permission gotcha: Explains that LINE requires a separate email-permission application via OpenID Connect settings, without which Weegloo rejects every sign-in server-side. - Use Case: A developer adding LINE social login to their Weegloo-powered app uses this Skill to collect the correct credentials and avoid the terminology and email-permission traps before creating the ServiceLogin resource. ## Quick Start Walk me through setting up LINE Login as the OAuth provider for my Weegloo ServiceLogin, including the callback URL and credentials I need.
