What problem does it solve? Integrating user authentication with the Overlens Identity Provider requires correctly implementing OAuth 2.1 with PKCE, token exchange, JWT validation, refresh rotation, and logout — a process with many failure points like exact redirect_uri matching, S256 code challenges, and cookie maxAge unit bugs. This Skill provides the complete framework-agnostic integration guide plus endpoint contracts, security rules, and troubleshooting references so the integration is done correctly the first time. ## Core Features & Use Cases - Full OAuth 2.1 + PKCE flow guidance: Step-by-step instructions for authorization code flow, token exchange, id_token validation via JWKS, refresh token rotation, and OIDC RP-initiated logout. - Complete endpoint reference: Request/response contracts for every IDP endpoint (authorize, token, signup, userinfo, logout, JWKS, OIDC discovery) in references/endpoints.md. - Security rules and troubleshooting: Non-negotiable rules (RS256 only, SameSite=Lax, PKCE mandatory) and diagnostics for common errors like invalid_client, PKCE validation failures, and disappearing cookies. - Use Case: You are adding Overlens SSO login to a custom web app that is not Next.js or Vite+BFF. This Skill walks through PKCE generation, the authorize redirect, callback handling, secure token storage, silent refresh, and logout, then points you to the conformance test suite to prove correctness. ## Quick Start Ask the assistant to integrate Overlens IDP login into your application and it will guide you through the OAuth 2.1 PKCE flow step by step.
