0 views collected around this technical thread.
This article explains how to extend an open‑source smart production management system with MCP support by creating SSE/HTTP endpoints, a token‑based MAP, and a McpService that scans, executes, and pushes results, and demonstrates client configuration using CherryStudio.
This article presents a comprehensive design for securing third‑party APIs by using Access Key/Secret Key pairs, timestamp and nonce validation, signature generation, token handling, HTTPS, rate limiting, logging, idempotency, versioning, standardized response formats and practical Java code examples to prevent tampering and replay attacks.
This article explains how to implement debounce functionality and prevent duplicate form submissions in PHP using session storage, providing step‑by‑step code examples for creating a debounce helper, generating and validating tokens, and integrating them into web forms.
This article explains the technical selection between JWT and session for authentication, compares their differences, advantages, and disadvantages, and provides a complete Java implementation—including token generation, Redis storage, login/logout, password update, and request interception—demonstrating why JWT was chosen for a distributed backend system.
This article explains the fundamentals of CSRF attacks, how they exploit authenticated users' cookies, and provides practical PHP techniques—including token generation and verification, request‑origin checks, secure cookie settings, and safe login/logout handling—to effectively protect web applications.
This article explains the fundamentals of QR code login, detailing how QR codes work, the token‑based authentication mechanism, and the step‑by‑step process—including QR code generation, scanning, temporary token exchange, and final confirmation—that enables secure cross‑device login without exposing passwords.
This article explains the fundamentals of QR code login, detailing how QR codes convey unique IDs, the token‑based authentication process, the steps from QR generation to device verification, and the security considerations involved in implementing scan‑to‑login across web and mobile platforms.
This article demonstrates practical implementations of session-based and token-based authentication, including JWT and a dual-token (access and refresh) mechanism, using Python's requests library, and explains how to obtain, use, and refresh tokens for protected API endpoints in automated testing.
This article explains the concept of Single Sign-On, its advantages, and two practical implementations using ticket‑based authentication and encrypted user data exchange between Service A and Service B, complete with database schema, configuration files, and full Java code examples.
This article explains the fundamentals of token‑based authentication, the drawbacks of fixed token lifetimes, and presents multiple silent‑refresh techniques—including double‑token mechanisms, front‑end timers, server‑side proactive refresh, and concurrency‑safe lock strategies—along with practical code examples and performance considerations for high‑concurrency scenarios.
Starting with Kubernetes 1.24, automatic ServiceAccount token Secrets are deprecated; this guide explains the core changes, shows how to manually create token Secrets, extract tokens, and verify permissions using command‑line, API calls, and RBAC inspection, plus common troubleshooting steps.
The article presents a comprehensive design for securing third‑party API calls by generating unique Access Key/Secret Key pairs, defining permission scopes, implementing signature generation and verification, employing timestamps and nonces to prevent replay attacks, and outlining practical API endpoint specifications and response standards.
This guide explains how to create a seamless auto‑login feature by persisting a token in a cookie after the first successful login, storing the token in Redis, and validating it on subsequent visits, complete with Java Spring code examples.
This article presents a comprehensive design for securing third‑party API calls by generating unique Access Key/Secret Key pairs, defining permission granularity, implementing signature generation with timestamps and nonces, handling token lifecycle, and providing concrete Java and SQL code examples for practical deployment.
Hotlinking attacks steal popular media by fetching resources from major platforms, but developers can protect assets using anti-leech methods such as Nginx referer checks, SpringBoot filters, token validation, timestamp verification, and graphical captchas, each with strengths and limitations against forged requests.
This article explains how to prevent duplicate order submissions in e‑commerce systems by using a token mechanism and Redis‑based distributed locks within a Spring Boot backend, detailing the workflow, code implementation, and best‑practice optimizations for idempotent processing.
This article presents a comprehensive design scheme for third‑party API interfaces, covering access‑key/secret‑key generation, permission segmentation, signature flow and rules, anti‑replay mechanisms, token handling, and concrete Java code examples for secure request validation.
This article explains how QR code login works by describing QR code fundamentals, token‑based authentication, and the step‑by‑step process—including QR generation, scanning, state transitions, and final confirmation—that enables a mobile device to securely authenticate a PC session.
This article presents a comprehensive design for securing third‑party APIs, covering permission segmentation, AK/SK generation, signature workflow and rules, anti‑replay mechanisms, token handling, detailed API endpoint specifications, and best‑practice security measures with illustrative Java code examples.
This article reviews four widely used authentication mechanisms—HTTP Basic Authentication, session‑cookie, token‑based verification (including JWT), and OAuth—explaining their workflows, security characteristics, implementation details with Node.js/Express code samples, and comparative advantages for different application scenarios.