Enforce PKCE, RBAC, and session policies for OAuth middleware.
npx skills add https://github.com/Vincri126/MCO-Template --skill auth-middleware
Please help me install this Agent Skill. Skill: auth-middleware Source: https://github.com/Vincri126/MCO-Template/tree/main/.orchestrator/skills/auth-middleware Command: npx skills add https://github.com/Vincri126/MCO-Template --skill auth-middleware
This Skill codifies the authentication and authorization architecture needed to securely layer Google and Microsoft OAuth flows on top of Supabase, preventing misconfigurations and ensuring middleware can enforce RBAC, session policies, and QA gates without blind spots.
Ask auth-middleware to review your Google and Microsoft OAuth configuration, ensure Supabase middleware enforces PKCE and RBAC, and summarize the security guardrails before deployment.
High-intent search queries and answers about installing and using this skill.
To enforce RBAC and PKCE in Next.js middleware, you configure Supabase auth layers to validate session continuity and apply security gates before routing. This ensures token refresh monitoring and role-based access control across SPAs and backend services.
Yes, Supabase works with Google and Microsoft OAuth for production authentication by layering Entra ID and Google Workspace APIs on top of its auth. This integration requires configuring PKCE enforcement and token refresh strategies to prevent misconfigurations.
Securing OAuth session continuity across mobile clients and SPAs requires production-grade middleware that monitors token refresh cycles and enforces security headers. This approach prevents session hijacking and maintains access continuity across diverse client platforms.
You run a bash QA gate script that scans your codebase for hardcoded secrets, validates PKCE usage, checks CORS and cookie policies, and verifies Supabase RLS readiness. This documents architecture decisions and prevents blind spots before merging auth changes.
Microsoft Graph API integrations fail with Supabase OAuth when middleware lacks proper RBAC enforcement and token refresh monitoring. Aligning OAuth flows with Entra ID configurations and applying session policies resolves access and continuity issues.
Yes, auth-middleware supports production-grade Node deployments alongside Next.js by applying OAuth security gates, RBAC enforcement, and session management. It handles PKCE enforcement and token monitoring across both environments.
BaraArdiwinataImplement OAuth2/OIDC identity provider integration in Next.js with PKCE and Supabase Admin API.
roedyrustamAudit Supabase deployments for RLS, RBAC, secrets, and edge-layer security gaps.
InnerScopeHearingManage OneDrive files and folders via Microsoft Graph API.
CleanExpoDocument authentication and authorization patterns to prevent auth drift across SYNTHEX services.
