add-external-oauth

Implement OAuth2/OIDC identity provider integration in Next.js with PKCE and Supabase Admin API.

1|Updated May 26, 2026
One-click install
npx skills add https://github.com/BaraArdiwinata/hackathon-sima-arome --skill add-external-oauth-baraardiwinata
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: add-external-oauth
Source: https://github.com/BaraArdiwinata/hackathon-sima-arome/tree/main/.agents/skills/add-external-oauth
Command: npx skills add https://github.com/BaraArdiwinata/hackathon-sima-arome --skill add-external-oauth-baraardiwinata

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill solves the challenge of adding secure OAuth/OIDC identity provider integration to Next.js applications using Supabase, which requires PKCE, user provisioning via Supabase Admin API, and session management.

Core Features & Use Cases

  • OAuth/OIDC Integration: Seamlessly integrates with popular IDPs like Azure AD, Okta, Auth0, Google, and more.
  • User Provisioning: JIT (Just-In-Time) user provisioning directly from external IDP.
  • Session Management: Securely manages user sessions without deployment access to Supabase.
  • Use Case: Ideal for self-hosted Supabase instances where IDP configuration is inaccessible, enabling SSO and secure authentication for users.

Quick Start

Invoke the skill with add-external-oauth --provider=provider_name --return_to=https://your-app.com/callback.

Frequently Asked Questions about add-external-oauth

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I add external OAuth to a Next.js app using a self-hosted Supabase instance?

You can add external OAuth to Next.js with self-hosted Supabase by implementing an OAuth proxy flow with PKCE and handling user provisioning directly via the Supabase Admin API, bypassing the need for IDP deployment access.

What is Just-In-Time user provisioning in Supabase OAuth flows?

Just-In-Time (JIT) user provisioning in Supabase OAuth flows automatically creates and updates user identities directly from external IDP claims during the OIDC login process, ensuring seamless authentication without manual account setup.

Can I integrate Azure AD or Okta with Next.js and Supabase using OAuth?

Yes, you can integrate identity providers like Azure AD, Okta, and Auth0 with Next.js and Supabase by configuring the OAuth client to handle OIDC and PKCE proxy flows for secure authentication.

How does PKCE secure the OAuth proxy flow for Next.js applications?

PKCE secures the OAuth proxy flow by using a dynamic code verifier and challenge, preventing malicious interception of authorization codes during the Next.js client and IDP token exchange process.

Do I need deployment access to Supabase to configure external OIDC providers?

No, you do not need deployment access to Supabase to configure external OIDC providers; the integration handles user provisioning and session management directly from Next.js using the Supabase Admin API.

How do I manage user sessions after external OAuth login in Next.js?

You manage user sessions after external OAuth login in Next.js by securely handling the session tokens generated through the Supabase Admin API, maintaining authentication state without direct IDP deployment configuration.