nodeops-auth

Included with Lifetime

$97 forever

Add NodeOps PKCE OAuth authentication to a Next.js app. Trigger when the user wants to set up NodeOps login, integrate NodeOps OAuth, add @nodeops-createos/integration-oauth, or connect a Next.js project to NodeOps identity/SSO. Also trigger on "add NodeOps auth", "setup NodeOps authentication", or "add NodeOps login".

Web Dev

What this skill does


# NodeOps Auth Setup

Add NodeOps PKCE OAuth to an existing Next.js (App Router) project.

## Prerequisites

Before starting, verify the project is compatible:

- **App Router required**: Check if `app/` directory exists. If only `pages/` exists, stop and tell the user: "This skill only supports Next.js App Router. Your project uses Pages Router."
- **Next.js required**: Check `package.json` for `next` in dependencies. If missing, stop and tell the user this is a Next.js-only package.

## Idempotency

Before each step, check if the work is already done. Skip steps that are already complete:
- If `@nodeops-createos/integration-oauth` is already in `package.json` dependencies, skip install.
- If `app/api/auth/me/route.ts` and `app/api/auth/token/route.ts` already exist, skip route creation.
- If `AuthProvider` from `@nodeops-createos/integration-oauth` is already imported in the layout, skip wrapping.
- If `app/callback/page.tsx` (or `.jsx`) already exists, skip callback page creation.
- If `.env.example` already exists and contains `NODEOPS_`, skip env file creation.

## Steps

1. **Detect project setup** — read `package.json` and check for lock files:
   - Package manager: if `pnpm-lock.yaml` exists → pnpm, if `yarn.lock` exists → yarn, else → npm
   - TypeScript: if `tsconfig.json` exists use `.ts`/`.tsx` extensions, else `.js`/`.jsx`
   - Confirm `app/` directory exists (App Router). If only `pages/` exists, stop.
   - Confirm `next` is in dependencies. If not, stop.

2. **Install the package** — run the appropriate install command:
   - npm: `npm install @nodeops-createos/integration-oauth`
   - pnpm: `pnpm add @nodeops-createos/integration-oauth`
   - yarn: `yarn add @nodeops-createos/integration-oauth`
   - **If install fails**: check if the user has network access and the registry is reachable. Suggest running the command manually if it keeps failing.

3. **Create the API routes** — create two separate route files, creating directories as needed:

   `app/api/auth/me/route.ts` (or `.js`):
   ```ts
   export { GET } from '@nodeops-createos/integration-oauth/server/me';
   ```

   `app/api/auth/token/route.ts` (or `.js`):
   ```ts
   export { POST } from '@nodeops-createos/integration-oauth/server/token';
   ```

4. **Wrap layout with AuthProvider** — read the root layout file. It could be `app/layout.tsx`, `app/layout.jsx`, `app/layout.js`, or `app/layout.ts`. Find whichever exists.
   - Add the import at the top of the file:
     ```tsx
     import { AuthProvider } from '@nodeops-createos/integration-oauth';
     ```
   - Find `{children}` inside the `<body>` tag. Wrap it with `<AuthProvider>`:
     ```tsx
     <AuthProvider>{children}</AuthProvider>
     ```
   - **Do NOT add "use client" to the layout.** `AuthProvider` is already marked `"use client"` internally — it works fine when imported from a Server Component layout.
   - **If the layout already has other providers** (e.g., ThemeProvider, QueryClientProvider), nest `<AuthProvider>` alongside them. Do NOT remove or replace existing providers.
   - **If `{children}` is not directly inside `<body>`** (e.g., it's inside a wrapper div or fragment), wrap wherever `{children}` appears.
   - **If no layout file exists**, stop and tell the user to create a root layout first.

5. **Create the callback page** — ask the user: "Where should users be redirected after login? (default: /dashboard)". Use their answer as the `redirectTo` value. Then create `app/callback/page.tsx` (or `.jsx`):
   ```tsx
   "use client";
   import { useCallbackHandler } from "@nodeops-createos/integration-oauth";

   export default function Callback() {
     const { loading, error } = useCallbackHandler({ redirectTo: "/dashboard" });

     if (loading) return (
       <div style={{ display: "flex", justifyContent: "center", alignItems: "center", height: "100vh" }}>
         <p>Signing in...</p>
       </div>
     );
     if (error) return <p>Login failed: {error}</p>;
     return null;
   }
   ```

6. **Create `.env.example`** — create this file at the project root:
   ```
   # ── Client-side (exposed to browser via NEXT_PUBLIC_ prefix) ──────────────────
   NEXT_PUBLIC_NODEOPS_AUTH_URL=https://id.nodeops.network/oauth2/auth
   NEXT_PUBLIC_NODEOPS_CLIENT_ID=your_client_id_here
   NEXT_PUBLIC_NODEOPS_REDIRECT_URI=http://localhost:3000/callback
   NEXT_PUBLIC_NODEOPS_SCOPES=offline_access offline openid

   # ── Server-side only (never sent to browser) ──────────────────────────────────
   NODEOPS_CLIENT_SECRET=your_client_secret_here
   NODEOPS_TOKEN_URL=https://id.nodeops.network/oauth2/token
   NODEOPS_USERINFO_URL=https://autogen-v2-api.nodeops.network/v1/users/me
   ```

7. **Create `.env.local`** — if `.env.local` does not already exist, copy `.env.example` to `.env.local` and remind the user to fill in `NEXT_PUBLIC_NODEOPS_CLIENT_ID` and `NODEOPS_CLIENT_SECRET` with their credentials from the NodeOps developer portal. If `.env.local` already exists, append the missing `NODEOPS_` vars only — do NOT overwrite existing values.

8. **Check `.gitignore`** — read `.gitignore` (if it exists). If `.env.local` is NOT listed, add it to prevent leaking secrets. Also ensure `.env` is listed. If no `.gitignore` exists, create one with at least:
   ```
   .env
   .env.local
   ```

9. **Docker/container deployment** — check if a `Dockerfile` exists in the project root. If it does, verify it handles NodeOps env vars correctly and warn the user if not. If the user asks about Docker or deployment, create or update the Dockerfile.

   **Critical**: `NEXT_PUBLIC_*` vars are baked into the JS bundle at **build time** by Next.js. They must be set as `ENV` or `ARG` in the Dockerfile **before** `RUN npm run build`. Setting them only at runtime does nothing — the bundle will contain `undefined`.

   The two categories of vars:

   | Variable | When needed | Why |
   |---|---|---|
   | `NEXT_PUBLIC_NODEOPS_AUTH_URL` | Build time | Inlined into client JS bundle |
   | `NEXT_PUBLIC_NODEOPS_CLIENT_ID` | Build time | Inlined into client JS bundle |
   | `NEXT_PUBLIC_NODEOPS_REDIRECT_URI` | Build time | Inlined into client JS bundle |
   | `NEXT_PUBLIC_NODEOPS_SCOPES` | Build time | Inlined into client JS bundle |
   | `NODEOPS_CLIENT_SECRET` | Runtime only | Read by API route on each request |
   | `NODEOPS_TOKEN_URL` | Runtime only | Read by API route on each request |
   | `NODEOPS_USERINFO_URL` | Runtime only | Read by API route on each request |

   > **CreateOS note:** CreateOS uses the Dockerfile when one is present. Use a **single-stage** Dockerfile only — multi-stage builds with `COPY --from=builder` fail on this platform. Remove the Dockerfile entirely to fall back to CreateOS's default install/run commands. See the CreateOS section (step 10) for the runtime config workaround for `NEXT_PUBLIC_*` vars.

   Example Dockerfile (single-stage, compatible with CreateOS):
   ```dockerfile
   FROM node:20-alpine
   WORKDIR /app
   COPY package*.json ./
   RUN npm ci

   COPY . .

   # NEXT_PUBLIC_* must be present at build time — they get baked into the JS bundle
   ARG NEXT_PUBLIC_NODEOPS_AUTH_URL=https://id.nodeops.network/oauth2/auth
   ARG NEXT_PUBLIC_NODEOPS_CLIENT_ID
   ARG NEXT_PUBLIC_NODEOPS_REDIRECT_URI
   ARG NEXT_PUBLIC_NODEOPS_SCOPES=offline_access offline openid

   ENV NEXT_PUBLIC_NODEOPS_AUTH_URL=$NEXT_PUBLIC_NODEOPS_AUTH_URL
   ENV NEXT_PUBLIC_NODEOPS_CLIENT_ID=$NEXT_PUBLIC_NODEOPS_CLIENT_ID
   ENV NEXT_PUBLIC_NODEOPS_REDIRECT_URI=$NEXT_PUBLIC_NODEOPS_REDIRECT_URI
   ENV NEXT_PUBLIC_NODEOPS_SCOPES=$NEXT_PUBLIC_NODEOPS_SCOPES

   # Server-side vars — only needed at runtime, read per-request by API routes
   ENV NODEOPS_CLIENT_SECRET=""
   ENV NODEOPS_TOKEN_URL=https://id.nodeops.network/oauth2/token
   ENV NODEOPS_USERINFO_URL=https://autogen-v2-api.nodeops.network/v1/users/me

   RUN npm run build

   EXPOSE 3000
   CMD ["npm", "start"]
   ```

   Also ensure `.dockerignore` excludes `.env.local`:
   ```
   .env
   .env.local

Files: 1

Size: 12.2 KB

Complexity: 17/100

Category: Web Dev

Source: https://github.com/nodeops-app/skills/tree/main/skills/nodeops-auth

Related in Web Dev

generating-lwc-components

Included

Lightning Web Components with PICKLES methodology and 165-point scoring. Use this skill when the user creates or edits LWC components, builds wire service patterns, or writes Jest tests for LWC. TRIGGER when: user creates/edits LWC components, touches lwc/**/*.js, .html, .css, .js-meta.xml files, or asks about wire service, SLDS, or Jest LWC tests. DO NOT TRIGGER when: Apex classes (use generating-apex), Aura components, or Visualforce.

Web Devscripts

tanstack-query

Included

Manage server state in React with TanStack Query v5. Set up queries with useQuery, mutations with useMutation, configure QueryClient caching strategies, implement optimistic updates, and handle infinite scroll with useInfiniteQuery. Use when: setting up data fetching in React projects, migrating from v4 to v5, or fixing object syntax required errors, query callbacks removed issues, cacheTime renamed to gcTime, isPending vs isLoading confusion, keepPreviousData removed problems.

Web Devscripts

document-processor-api

Included

Process documents with Nutrient DWS. Use when the user wants to generate PDFs from HTML or URLs, convert Office/images/PDFs, assemble or split packets, OCR scans, extract text/tables/key-value pairs, redact PII, watermark, sign, fill forms, optimize PDFs, or produce compliance outputs like PDF/A or PDF/UA. Triggers include convert to PDF, merge these PDFs, OCR this scan, extract tables, redact PII, sign this PDF, make this PDF/A, or linearize for web delivery.

Web Devscripts

nutrient-document-processing

Included

Web Devscripts

tanstack-query

Included

Manage server state in React with TanStack Query v5. Covers useMutationState, simplified optimistic updates, throwOnError, network mode (offline/PWA), and infiniteQueryOptions. Use when setting up data fetching, fixing v4→v5 migration errors (object syntax, gcTime, isPending, keepPreviousData), or debugging SSR/hydration issues with streaming server components.

Web Devscripts

accelint-nextjs-best-practices

Included

Next.js performance optimization and best practices. Use when writing Next.js code (App Router or Pages Router); implementing Server Components, Server Actions, or API routes; optimizing RSC serialization, data fetching, or server-side rendering; reviewing Next.js code for performance issues; fixing authentication in Server Actions; or implementing Suspense boundaries, parallel data fetching, or request deduplication.

Web Devscripts