Token导航 LogoToken导航

Agent Skill · 开发

express-oauth2-jwt-bearer(express oauth2 JWT bearer 安全)

用于辅助安全审计、权限检查、凭据风险、认证流程和常见漏洞排查。它适合让 Agent 梳理敏感配置、检查依赖风险、分析鉴权逻辑或生成安全复核清单。使用时不能把工具输出直接当最终结论,涉及密钥、令牌、用户数据或生产系统时,应先确认最小权限、脱敏方式和操作边界。

express-oauth2-jwt-bearer 是开发类 Agent Skill,可用宿主为 Codex、Claude、Cursor、Gemini CLI,通过GitHub 仓库获取,权限为接触敏感数据;许可证信息还不明确,第三方扫描有提醒项,按安装量在开发类的 21,746 个 Skill 里排第 11,887。

总安装 1,533周安装 62GitHub Stars 17下载 481核验 2026-05-01

安装说明

本站只整理中文说明,不托管安装包,也不代用户安装。
GitHub
许可证
unknown

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:express-oauth2-jwt-bearer(express oauth2 JWT bearer 安全)
来源仓库:https://github.com/auth0/agent-skills
仓库路径:skills/express-oauth2-jwt-bearer
安装命令:
npx skills add https://github.com/auth0/agent-skills --skill express-oauth2-jwt-bearer
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 npx skills 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

skills.shnpx skills
npx skills add https://github.com/auth0/agent-skills --skill express-oauth2-jwt-bearer

这个 Skill 是做什么的

开发类 Skill 面向写代码、改代码和排查问题,一般会读写仓库文件,部分还会执行构建或测试命令。

为 Auth0 JWT Bearer Token 提供 Express 中间件验证支持。自动处理令牌提取、签名校验、受众与签发者验证流程。遵循 RFC 6750 标准,减少手动解析 JWT 的安全隐患。需配合 Auth0 控制台获取正确的 audience 与 issuer 配置参数。

express-oauth2-jwt-bearer 属于开发类 Skill,可作为该场景下的辅助能力补充。

来源仓库内路径:skills/express-oauth2-jwt-bearer

上手步骤

4 步
  1. 1

    确认自己的宿主工具

    公开资料标注支持 Codex、Claude、Cursor、Gemini CLI;先确认自己用的是其中之一,再按对应工具的 Skills 目录放置。

  2. 2

    拿到安装命令

    可以直接复制的命令是 npx skills add https://github.com/auth0/agent-skills --skill express-oauth2-jwt-…;命令里的占位符换成自己的路径或密钥再执行。

  3. 3

    安装后重启宿主

    命令执行完要完全退出宿主工具再打开,让新装的 Skill 被重新扫描到,否则列表里可能看不到。

  4. 4

    按最小权限试用

    它需要接触敏感数据,先在测试目录或测试账号里跑,确认没问题再放到正式项目。

常见问题

6 条

express-oauth2-jwt-bearer 怎么安装?

在终端执行 npx skills add https://github.com/auth0/agent-skills --skill express-oauth2-jwt-bearer。装完完全退出宿主工具再打开,让它重新扫描本地 Skill。

express-oauth2-jwt-bearer 支持哪些 AI 工具?

公开资料标注支持 Codex、Claude、Cursor、Gemini CLI。其他工具只要能读取本地 Skill 目录,一般也能手动放进去,但要自己确认触发方式是否一致。

express-oauth2-jwt-bearer 需要什么权限?

权限级别是接触敏感数据。该 Skill 可能接触密钥、Token、环境变量或敏感配置,应进入高风险复核队列,默认不自动发布。

express-oauth2-jwt-bearer 是免费的吗?

公开资料没有标注明确许可证,收费和商用限制都无法确认。正式使用前请到来源仓库核对授权说明。

express-oauth2-jwt-bearer 用的人多吗?

公开数据是累计安装 1,533 次,近一周安装 62 次,下载 481 次,GitHub 17 星。这些数字来自第三方目录统计,只能当作热度参考,不代表质量或安全性。

express-oauth2-jwt-bearer 安全吗?

第三方扫描有提醒项,说明存在需要人工确认的行为。安装前请打开源码看清它读了什么、联网到哪里。

值得选的地方和要先想清楚的地方

值得选的地方

  • 同时适配 4 种工具,换客户端不用重新找替代品。

先想清楚的地方

  • 需要接触敏感数据,装到常用环境前要先评估影响面。
  • 许可证没有明确标注,能不能商用、能不能再分发都不确定。
  • 第三方扫描存在提醒项或未通过项,需要人工逐条确认。
  • 第三方目录整理,版本更新和行为细节以来源仓库为准。

适不适合你

更适合

  • 已经在用 Codex,想直接扩展它能力的人。
  • 需要处理开发类任务、又不想每次都手写提示词的人。

不太适合

  • 环境里有大量密钥、凭证,不方便给第三方 Skill 读取的人。
  • 需要明确授权才能用到公司项目里的场景。
  • 需要厂商级技术支持和 SLA 的生产系统。

开发类 Skill 对比

6 个同类
Skill总安装GitHub 星权限许可证扫描
skill-vetter

技能审查员 · OpenClaw

8,779,018986操作浏览器MIT-0通过
ontology

本体论 · OpenClaw

6,636,960576只读MIT-0通过
entra-app-registration

内部应用程序注册 · Codex、Claude

6,631,872764接触敏感数据未明确通过
entra-app-registration

内部应用程序注册 · Codex、Claude

3,757,680201接触敏感数据未明确通过
nano-banana-pro

纳米香蕉专业版 · OpenClaw

3,526,898364接触敏感数据MIT-0有提醒
express-oauth2-jwt-bearer

express oauth2 JWT bearer 安全 · 本页

1,53317接触敏感数据未明确有提醒

按安装量取同分类前几名;数字来自第三方目录统计,只作热度参考,不代表质量结论。

SKILL.md 原文

Node OAuth2 JWT Bearer Integration

The express-oauth2-jwt-bearer package provides Express middleware for validating Auth0 JWT Bearer access tokens. It handles token extraction, signature verification, audience and issuer validation, and expiry checks per RFC 6750 — letting you focus on business logic rather than JWT parsing.

Agent instruction: Before providing SDK setup instructions, fetch the latest release version by running: ``bash gh api repos/auth0/node-oauth2-jwt-bearer/releases/latest --jq '.tag_name' ` Use the returned version in all package.json` dependency lines instead of any hardcoded version below.

Prerequisites

  • Node.js 18+ (20+ recommended; required for bootstrap script automation)
  • Express 4.x or 5.x
  • npm or yarn
  • An Auth0 account with a configured API (Resource Server)
  • Auth0 CLI (for automatic setup): npm install -g @auth0/auth0-cli

When NOT to Use

Use CaseRecommended Skill
Building a server-side web app with login UI (Express sessions)auth0-express
Building a Next.js app with server-side authauth0-nextjs
Building a React/Angular/Vue SPAauth0-react, auth0-angular, auth0-vue
Building a React Native or mobile appauth0-react-native, auth0-android, auth0-swift
ASP.NET Core Web APIauth0-aspnetcore-api
Go API with JWT middlewarego-jwt-middleware
Python API (Flask/FastAPI)auth0-api-python
Node.js API using the older express-jwt packageexpress-jwt

Quick Start Workflow

Agent instruction: Follow these steps to integrate express-oauth2-jwt-bearer into the user's Node.js API project. 1. Fetch latest version (see instruction above). 2. Install the SDK: npm install express-oauth2-jwt-bearer 3. Configure Auth0 — follow references/setup.md. If the user already provided their Auth0 Domain and API Audience in the prompt, use them directly — skip the bootstrap script and do NOT call AskUserQuestion to re-confirm. Otherwise, offer automatic setup via bootstrap script or manual setup. 4. Set up middleware — add to app.js or server.js: ` import {auth} from 'express-oauth2-jwt-bearer'; const checkJwt = auth({issuerBaseURL: https://${process.env.AUTH0_DOMAIN}, audience: process.env.AUTH0_AUDIENCE,}); app.use(checkJwt); // apply globally, or per-route 5. **Protect endpoints** — apply middleware globally or to specific routes: // Global protection app.use(checkJwt); // Or per-route app.get('/api/private', checkJwt, (req, res) => {res.json({sub: req.auth.payload.sub});}); 6. **Add RBAC** (optional) — use requiredScopes() or claimIncludes() for permission-based access: import {auth, requiredScopes, claimIncludes} from 'express-oauth2-jwt-bearer'; app.get('/api/messages', checkJwt, requiredScopes('read:messages'), (req, res) => {res.json({messages: []});}); **Important:** requiredScopes accepts a single argument — a space-separated string or an array. Do NOT pass multiple string arguments: requiredScopes('read:msg', 'write:msg') silently ignores everything after the first. Use requiredScopes('read:msg write:msg') or requiredScopes(['read:msg', 'write:msg']) instead. 7. **Verify the integration** — build and test: node server.js curl http://localhost:3000/api/private # should return 401 curl -H "Authorization: Bearer <token>" http://localhost:3000/api/private # should return 200 8. **Failcheck:** If the server fails to start or tokens are rejected unexpectedly, check references/api.md for common issues. After 5-6 failed iterations, use AskUserQuestion` to ask the user for more details about their environment.

Detailed Documentation

  • Setup Guide — Auth0 API registration,.env configuration, bootstrap script for automated setup, and secret management
  • Integration Patterns — Protected endpoints, RBAC with scopes and claims, DPoP, CORS setup, error handling, and testing with curl
  • API Reference & Testing — Full configuration options, claims reference, complete code example, testing checklist, and common issues

Common Mistakes

MistakeSymptomFix
Created an Application instead of an API in Auth0 DashboardToken validation fails; wrong audienceCreate a new API (Resource Server) in Auth0 Dashboard → APIs
Audience doesn't match API identifier exactly401 Unauthorized — "Audience mismatch"Copy the exact API Identifier string from Auth0 Dashboard → APIs
Domain includes https:// prefixError: Invalid URL at startupUse hostname only: your-tenant.us.auth0.com, not https://...
Checking scope claim instead of permissions for RBAC403 always returned or permissions ignoredUse requiredScopes() for scope-based RBAC; use claimIncludes('permissions', 'read:data') for Auth0 RBAC permission claims
CORS not configured before auth middlewarePreflight OPTIONS requests return 401Add cors() middleware before auth() in the middleware chain
.env file not loadedundefined for domain/audienceAdd import 'dotenv/config' at the top of the entry file
req.auth is undefinedTypeError: Cannot read properties of undefinedVerify checkJwt middleware runs before the handler

Related Skills

Quick Reference

Core Middleware

FunctionDescriptionReturns
auth(options?)JWT Bearer validation middlewareHandler — 401 if token invalid/missing
requiredScopes(scopes)Validates token has all required scopesHandler — 403 if scopes missing
scopeIncludesAny(scopes)Validates token has at least one scopeHandler — 403 if no match
claimEquals(claim, value)Validates a claim equals a valueHandler — 401 if mismatch
claimIncludes(claim,...values)Validates claim includes all valuesHandler — 401 if incomplete
claimCheck(fn, desc?)Custom claim validation functionHandler — 401 if fn returns false

Configuration Options

OptionTypeDescription
issuerBaseURLstringAuth0 domain with https:// (required unless using env vars)
audiencestringAPI Identifier from Auth0 Dashboard (required unless using env vars)
tokenSigningAlgstringSigning algorithm (default: RS256; use HS256 for symmetric)
authRequiredbooleanSet false to make authentication optional (default: true)
clockTolerancenumberClock skew tolerance in seconds (no default; undefined unless set)
dpopDPoPOptionsDPoP configuration (see integration.md)

Environment Variables

VariableDescription
ISSUER_BASE_URLAuth0 domain with https:// (auto-detected by SDK)
AUDIENCEAPI Identifier (auto-detected by SDK)

Request Object

After successful validation, req.auth contains:

req.auth.payload    // Decoded JWT payload (sub, iss, aud, exp, permissions, etc.)
req.auth.header     // JWT header (alg, typ, kid)
req.auth.token      // Raw JWT string

SDK Architecture

The node-oauth2-jwt-bearer monorepo contains three packages:

PackagePurpose
express-oauth2-jwt-bearerMain package. Express middleware for JWT Bearer validation. Published to npm.
access-token-jwtLow-level JWT verification utilities (used internally).
oauth2-bearerRFC 6750 Bearer token extraction (used internally).

In practice, you only install and import express-oauth2-jwt-bearer.

Auth Flow Comparison

Auth PatternSDKWhen to Use
JWT Bearer (stateless)express-oauth2-jwt-bearerAPIs called by SPAs, mobile apps, M2M clients
Session-based (stateful)@auth0/express-openid-connectWeb apps with login UI and server-side sessions

Testing Quick Reference

# Get test token from Auth0 Dashboard → APIs → your API → Test tab
# Copy the token, then:

# 1. Verify 401 on protected route (no token)
curl -v http://localhost:3000/api/private

# 2. Verify 200 with valid token
curl -H "Authorization: Bearer <paste-token-here>" http://localhost:3000/api/private

# 3. Verify 403 with valid token but missing scope
curl -H "Authorization: Bearer <paste-token-here>" http://localhost:3000/api/admin

# 4. Verify CORS preflight
curl -v -X OPTIONS http://localhost:3000/api/private \
  -H "Origin: http://localhost:5173" \
  -H "Access-Control-Request-Method: GET" \
  -H "Access-Control-Request-Headers: Authorization"

References

平台分布

Codex

36.06%
按下载量换算173

Claude

27.15%
按下载量换算131

Cursor

17.99%
按下载量换算87

Gemini CLI

9.31%
按下载量换算45

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

可疑

权限和风险

接触敏感数据

该 Skill 可能接触密钥、Token、环境变量或敏感配置,应进入高风险复核队列,默认不自动发布。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。来源安全扫描存在提醒或未通过项,安装前请自行复核。目前只有一个公开来源,建议同时核对源仓库。

继续浏览同类 Skills