What problem does it solve? Setting up Kakao Login as an OAuth provider for Weegloo ServiceLogin requires navigating the Kakao Developers console, where mistakes like using the wrong app key, leaving the Client Secret disabled, or missing the email consent item silently break sign-in. This Skill provides the exact console steps and known gotchas so the integration works on the first attempt. ## Core Features & Use Cases - Kakao Developers walkthrough: Step-by-step instructions to create a Kakao app, activate Kakao Login, register the Redirect URI (https://auth.weegloo.com/v1/spaces/{spaceId}/login/oauth2/code/kakao), and obtain the clientId / clientSecret. - Gotcha prevention: Documents that the clientId is the REST API key (not the JavaScript or Native key) and that the Client Secret must be both generated and enabled. - Email requirement handling: Explains that Weegloo rejects sign-ins without an email and that Kakao gates the email scope behind consent items and Business app review. - Use Case: A developer adding Kakao social login to a Weegloo-hosted service uses this Skill to guide the product owner through the Kakao console and collect the blocking credentials before creating the ServiceLogin resource. ## Quick Start Walk me through setting up Kakao Login as the OAuth provider for my Weegloo ServiceLogin, including the Redirect URI to register and how to get the clientId and clientSecret.
