What problem does it solve? Every system that authenticates through the Overlens IDP needs a registered OAuth client, but registration only happens through an admin-only API with strict validation rules, and the client secret is shown exactly once. This Skill guides you through registering the client correctly on the first try — or, if you are not an Overlens admin, generates a ready-to-send registration request the Overlens team can apply without edits. ## Core Features & Use Cases - Three client types covered: confidential web (BFF with authorization_code + refresh_token), public PKCE (mobile/SPA with deep links, no secret), and M2M (client_credentials with empty redirectUris), each with the exact POST /admin/clients JSON payload. - Full validation rules: clientId regex, HTTPS/localhost/deep-link redirect URI rules with exact byte matching, allowed grant-type combinations, and the invalid combinations rejected with HTTP 400. - Registration-request mode for non-admins: interviews the user in plain language, validates everything locally, and emits the exact JSON payload plus a short covering message to send to the Overlens team. - Use Case: A developer says "I need a client_id and client_secret for my Next.js app". The Skill collects the callback URLs for production and localhost, builds the confidential-web payload, and either calls the admin API or produces the request for the Overlens team — warning that the secret must be copied immediately into a secret manager. ## Quick Start Ask the assistant to register an OAuth client for your system in the Overlens IDP, describing your app type and callback URLs.
