'jwt' 검색 결과

Hunt JSON Web Token (JWT) vulnerabilities — alg=none bypass, RS256→HS256 key confusion, weak HMAC secret cracking, kid path traversal, JWKS injection, jku/x5u header attacks, embedded JWK confusion, expired-token acceptance, claim mutability, and token replay. Use when an app uses JWT for authentication or stateless sessions.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Exploit implementations of JSON Web Tokens (JWT) through algorithmic confusion (e.g., RS256 to HS256), "none" algorithm attacks, and signature stripping. Use this skill to forge administration tokens and achieve unauthenticated Account Takeover (ATO) on REST APIs and modern web applications.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Identify and exploit Algorithm Confusion vulnerabilities in JSON Web Tokens (JWT). This skill details how to bypass signature verification by changing the signing algorithm from asymmetric (RS256) to symmetric (HS256) and using the public key as the symmetric secret.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Test APIs for authentication and authorization bypass vulnerabilities including JWT manipulation, OAuth2 flaws, API key leakage, broken authentication, and token forgery. Use this skill when assessing REST/GraphQL APIs for access control weaknesses, session management flaws, or credential handling issues. Covers JWT algorithm confusion, OAuth redirect manipulation, and rate limit bypass.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

JWT saldırıları — alg:none, HMAC brute-force, floating point bypass, CVE-2022-39227

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Rust 製バックエンド HTTP サーバーフレームワーク fandhe-backend のリファレンス。 fandhe-backend-core / -http / -routes。Server, BoundServer, Router（merge）, Handler。 拡張点 Middleware（on_response_with_status）/ UpgradeHandler / RequestGate / Interceptor。 Diagnostics, StreamingResponse, SetCookie session（__Host-）, sans-IO HTTP/1.1, graceful shutdown。 プラグイン cors, websocket（WsSender）, graphql, openapi, webrtc, jwt（JwtGate, JwtPolicy）, csrf（CsrfGate）。

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Provides JWT authentication and authorization patterns for Spring Boot 3.5.x covering token generation with JJWT, Bearer/cookie authentication, database/OAuth2 integration, and RBAC/permission-based access control using Spring Security 6.x. Use when implementing authentication or authorization in Spring Boot applications.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when implementing authentication, authorization, JWT tokens, security filters, password encoding, or any Spring Security configuration. Covers stateless JWT auth, token rotation, RBAC, and method-level security.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Implement secure authentication and authorization systems with JWT, OAuth2, Session-based auth, and RBAC. Use when: (1) implementing user login/signup, (2) setting up JWT tokens, (3) OAuth2 integration (Google, GitHub, etc.), (4) role-based access control (RBAC), (5) password hashing and validation, (6) session management, (7) API authentication middleware, (8) 2FA/MFA setup. Triggers: "authentication", "login", "JWT", "OAuth", "session", "password hash", "RBAC", "permissions", "2FA".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Java Spring Boot 서비스의 인증, 접근 권한, 입력 검증 등 보안 대책을 검토합니다. 비밀 정보 관리부터 API 호출 제한과 의존성까지 확인합니다.

• 인증과 접근 권한을 추가합니다
• API 입력 검증과 SQL을 검토합니다
• CSRF와 CORS 설정을 확인합니다

Implement or review login and access controls for applications and APIs. Helps define token lifetimes, session handling, and permissions for specific resources, with checks for user identity, organization boundaries, credential storage, and authentication failures.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Implement login and session management
• Review access controls for REST or GraphQL APIs
• Design social login or single sign-on

Trace OAuth and OIDC sign-in flows in a CTF sandbox, from redirects through token exchange to application acceptance. Show where tokens become a recognized identity or permission, and preserve the smallest reproducible flow.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Trace sign-in redirects and callback parameters
• Inspect state, nonce, and PKCE validation
• Check how tokens become application identity or permissions

Design and improve server-side applications using patterns for Node.js, Express, and Next.js API routes. Code examples cover API structure, database access, caching, authentication, error handling, and background jobs to guide implementation choices.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Organize API endpoints and application logic
• Reduce unnecessary database queries
• Add authentication and permission checks

Use prebuilt Zoom Video SDK interfaces to add video sessions to web applications. This reference covers framework integration, server-generated authentication tokens, chat and screen sharing settings, session cleanup, and troubleshooting for common installation and connection issues.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Adding a prebuilt video interface to a React or Next.js application
• Configuring chat and screen sharing for video sessions
• Implementing server-side authentication token generation

Build custom real-time video sessions in Flutter using flutter_zoom_videosdk. The skill guides package setup, session joining and leaving, event listeners that respond to SDK activity, and mobile platform integration.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Build custom video sessions in a Flutter app
• Implement session joining, leaving, and cleanup
• Connect SDK events to app actions

Embed Zoom meetings in native Android apps with guidance on authentication, joining and starting meetings, and SDK integration. Begin with the default interface, then move to a custom interface once authentication, permissions, and meeting state changes are stable.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Embedding Zoom meetings in an Android app
• Validating meeting join and start flows with the default interface
• Moving from the default interface to a custom interface

Plan encryption, TLS connections, digital signatures, and key management using established cryptographic libraries. Get guidance on choosing algorithms, storing passwords, rotating keys, and avoiding implementation mistakes such as reused nonces or comparisons that reveal information through timing.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Choosing encryption methods for stored data
• Reviewing TLS settings for encrypted connections
• Designing password storage and token signatures

Set up login, user management, and access rules in a Convex app. The skill connects the chosen authentication provider, links signed-in identities to app users when needed, and protects backend functions with identity and permission checks.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Adding login to a new Convex app
• Connecting an existing authentication provider
• Linking signed-in identities to app user records

Migrate Adobe integrations away from Service Account JWT, Photoshop v1, retired Lightroom Firefly Services, or drifting SDK/API contracts with canaries and rollback. Use when the task requires adobe end-of-life and contract migration. Trigger with "upgrade Adobe integration", "migrate Adobe JWT", or "Photoshop v2 migration".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

JWT and OAuth token attack playbook. Use when validating token trust, signing algorithms, key handling, claim abuse, bearer flows, and OAuth account-binding weaknesses.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

API authentication and JWT abuse playbook. Use when testing bearer tokens, API keys, claim trust, header spoofing, rate limits, and API auth boundary weaknesses.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when you need to design, review, or improve security in Quarkus applications — including Quarkus Security with JWT/OIDC, basic auth, @RolesAllowed / @Authenticated / @PermitAll, SecurityIdentity, permission checks, path-based authorization in configuration, exception mapping for auth failures, and sensitive-data-safe logging. This should trigger for requests such as Add Quarkus security support; Review Quarkus security configuration; Improve API authorization in Quarkus; Add JWT/OIDC security in Quarkus; Harden Quarkus authorization rules. Part of Plinth Toolkit

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when you need to design, review, or improve security in Spring Boot applications — including SecurityFilterChain, OAuth2/JWT resource server patterns, form login basics, method security (@PreAuthorize), CSRF and CORS for APIs, session fixation, security headers, exception handling, password encoding, and sensitive-data-safe logging. This should trigger for requests such as Add Spring Boot security support; Review Spring Boot security configuration; Improve API authorization in Spring Boot; Add JWT resource server security in Spring Boot; Harden Spring Boot security headers and CSRF settings. Part of Plinth Toolkit

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when you need to design, review, or improve security in Micronaut applications — including micronaut-security authentication, @Secured and intercept-url-map rules, JWT/session strategies, SecurityService checks, CORS, CSRF awareness for browser apps, rejection handlers, and sensitive-data-safe logging. This should trigger for requests such as Add Micronaut security support; Review Micronaut security configuration; Improve API authorization in Micronaut; Add JWT security in Micronaut; Harden Micronaut route authorization rules. Part of Plinth Toolkit

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.