building-api-authentication
Adds secure authentication mechanisms like JWT, OAuth2, and API keys to your API endpoints.
Install
mkdir -p .claude/skills/building-api-authentication && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/6352" && unzip -o skill.zip -d .claude/skills/building-api-authentication && rm skill.zipInstalls to .claude/skills/building-api-authentication
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Build secure API authentication systems with OAuth2, JWT, API keys,Key capabilities
- →Issue and validate JWT Bearer tokens
- →Implement OAuth 2.0 authorization code and client credentials flows
- →Manage refresh token rotation and revocation
- →Configure role-based and scope-based access control
- →Generate and validate hashed API keys
How it works
It establishes authentication middleware to verify tokens and roles, while using secure hashing for passwords and API keys. It manages token lifecycles through issuance, refresh rotation, and revocation.
Inputs & outputs
When to use building-api-authentication
- →Implement JWT issuance and validation
- →Set up OAuth 2.0 provider integration
- →Configure role-based access control (RBAC)
- →Secure API endpoints with custom middleware
About this skill
Building API Authentication
Overview
Build secure API authentication systems supporting JWT Bearer tokens, OAuth 2.0 authorization code and client credentials flows, API key management, and session-based authentication. Implement token issuance, validation, refresh rotation, revocation, and role-based access control (RBAC) with scoped permissions across all API endpoints.
Prerequisites
- Cryptographic library:
jsonwebtoken(Node.js),PyJWT(Python), orjjwt(Java) - Secure secret storage: environment variables, AWS Secrets Manager, or HashiCorp Vault for JWT signing keys
- Database table for user credentials, refresh tokens, and API key storage
- Bcrypt or Argon2 for password hashing (never store plaintext passwords)
- OAuth 2.0 provider credentials for third-party auth integration (Google, GitHub, Auth0)
Instructions
- Examine existing authentication setup using Grep and Read, identifying current auth mechanisms, middleware placement, and any endpoints bypassing authentication.
- Implement JWT token issuance on successful login: sign with RS256 (asymmetric) or HS256 (symmetric), including
sub(user ID),iat,exp(15-minute access token),roles, andscopesin the payload. - Create authentication middleware that extracts the Bearer token from the
Authorizationheader, verifies the signature and expiration, and injects the decoded user context into the request object. - Implement refresh token rotation: issue a long-lived refresh token (30 days) alongside the access token, store a hash of the refresh token in the database, and rotate on each refresh (invalidating the previous token).
- Build role-based access control (RBAC) middleware that checks
user.rolesagainst endpoint-required roles, supporting both role-level (admin,user) and scope-level (read:users,write:orders) authorization. - Add API key authentication as an alternative to JWT for machine-to-machine communication: generate cryptographically random keys, store hashed values, and validate against the
X-API-Keyheader. - Implement OAuth 2.0 client credentials flow for service-to-service authentication, with token caching and automatic renewal before expiration.
- Add brute-force protection on login endpoints: rate limit to 5 attempts per minute per IP, implement progressive lockout (15 min, 1 hour) after repeated failures, and log all authentication attempts.
- Write security tests covering: valid/invalid/expired tokens, refresh token rotation, role enforcement, API key validation, brute-force lockout, and token revocation.
See ${CLAUDE_SKILL_DIR}/references/implementation.md for the full implementation guide.
Output
${CLAUDE_SKILL_DIR}/src/auth/jwt.js- JWT token issuance, verification, and refresh logic${CLAUDE_SKILL_DIR}/src/auth/middleware.js- Bearer token authentication middleware${CLAUDE_SKILL_DIR}/src/auth/rbac.js- Role-based and scope-based access control middleware${CLAUDE_SKILL_DIR}/src/auth/api-keys.js- API key generation, hashing, and validation${CLAUDE_SKILL_DIR}/src/auth/oauth.js- OAuth 2.0 flow implementations${CLAUDE_SKILL_DIR}/src/routes/auth.js- Login, register, refresh, and logout endpoints${CLAUDE_SKILL_DIR}/tests/auth/- Authentication and authorization security tests
Error Handling
| Error | Cause | Solution |
|---|---|---|
| 401 Token Expired | JWT exp claim is in the past | Client should attempt token refresh; if refresh fails, redirect to login |
| 401 Invalid Signature | JWT signed with different key or tampered payload | Verify signing key matches between issuance and validation; check for key rotation issues |
| 403 Insufficient Scope | Authenticated user lacks required role/scope for endpoint | Return required scope in error body; log authorization failure with user and endpoint details |
| Refresh token reuse | Previously rotated refresh token used (possible token theft) | Invalidate all user sessions immediately; alert user of potential compromise; require re-authentication |
| API key leaked | API key exposed in client-side code, logs, or version control | Revoke compromised key immediately; issue replacement; scan for exposure source |
Refer to ${CLAUDE_SKILL_DIR}/references/errors.md for comprehensive error patterns.
Examples
JWT with refresh rotation: Login returns {accessToken (15min), refreshToken (30d)}; client stores refresh token securely; on 401, client calls POST /auth/refresh with old refresh token, receives new pair, old refresh token is invalidated.
Multi-provider OAuth: Support "Sign in with Google" and "Sign in with GitHub" using OAuth 2.0 authorization code flow, creating local user accounts on first sign-in and linking subsequent provider connections.
API key with scoped permissions: Generate API keys with specific scopes (read:analytics, write:webhooks), stored as SHA-256 hashes, displayed to the user only once at creation, with key rotation support.
See ${CLAUDE_SKILL_DIR}/references/examples.md for additional examples.
Resources
- RFC 7519 JSON Web Token (JWT): https://tools.ietf.org/html/rfc7519
- RFC 6749 OAuth 2.0 Authorization Framework
- OWASP Authentication Cheat Sheet: https://cheatsheetseries.owasp.org/
- Auth0 architecture patterns: https://auth0.com/docs/
When not to use it
- →Storing plaintext passwords
Prerequisites
Limitations
- →Requires secure storage for signing keys
- →Refresh token reuse invalidates all user sessions
How it compares
This approach integrates multi-layered security including refresh token rotation and scoped RBAC rather than simple session-based authentication.
Compared to similar skills
building-api-authentication side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| building-api-authentication (this skill) | 1 | 27d | Review | Advanced |
| senior-backend | 14 | 7mo | Review | Advanced |
| similarity-search-patterns | 3 | 2mo | No flags | Advanced |
| optimizing-performance | 1 | 2mo | Review | Intermediate |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by jeremylongshore
View all by jeremylongshore →You might also like
senior-backend
davila7
Comprehensive backend development skill for building scalable backend systems using NodeJS, Express, Go, Python, Postgres, GraphQL, REST APIs. Includes API scaffolding, database optimization, security implementation, and performance tuning. Use when designing APIs, optimizing database queries, implementing business logic, handling authentication/authorization, or reviewing backend code.
similarity-search-patterns
wshobson
Implement efficient similarity search with vector databases. Use when building semantic search, implementing nearest neighbor queries, or optimizing retrieval performance.
optimizing-performance
CloudAI-X
Analyzes and optimizes application performance across frontend, backend, and database layers. Use when diagnosing slowness, improving load times, optimizing queries, reducing bundle size, or when asked about performance issues.
caching-strategies
dadbodgeoff
Implement multi-layer caching with Redis, in-memory, and HTTP caching. Covers cache invalidation, stampede prevention, and cache-aside patterns.
pagination
dadbodgeoff
Implement cursor-based and offset pagination for APIs. Covers efficient database queries, stable sorting, and pagination metadata.
jsonapi
prowler-cloud
Strict JSON:API v1.1 specification compliance. Trigger: When creating or modifying API endpoints, reviewing API responses, or validating JSON:API compliance.