Guide Released for Integrating PDF Tamper Detection API into ASP.NET Core Apps

·1 views

A technical integration guide has been published for developers building PDF fraud detection into ASP.NET Core applications using the HTPBE tamper detection API. The guide targets .NET 8 and walks through a two-step API flow — submitting a PDF URL via POST and retrieving a verdict via GET — returning one of three statuses: intact, modified, or inconclusive. It covers a typed HTTP client built on IHttpClientFactory, snake_case JSON record DTOs, API key configuration, and a Polly-based retry policy for handling transient errors. A DocumentGate component is also introduced to translate the three verdicts into accept, reject, or review decisions for documents claiming institutional origin such as bank statements or payslips. The guide positions the tool as a structural forgery detection layer that complements existing KYC and identity verification stacks rather than replacing them.

Read the full story at DEV Community

This is an AI-generated summary. ShortSingh links to the original source for the complete article.

Discussion (0)

Open-Source Event Bus Links 32 MCP Servers Across Kenya's Public Coordination Domains

A developer has released africa-coord-bus, an open-source coordination layer designed to connect 32 Model Context Protocol servers built for Kenya's public service domains, including health, water, agriculture, and transport. Previously, each server operated in isolation, meaning a cholera outbreak flagged in Kisumu would not automatically trigger responses from water quality, emergency supply, or procurement systems. The package introduces a standard CoordinationEvent schema and an EventBus that routes cross-domain signals based on explicit, configurable rules. Unlike Western tech ecosystems that rely on years of existing API integrations, East African digital infrastructure is being built from scratch on MCP, making a shared coordination layer essential from the outset. The tool is available for installation via PyPI, with source code hosted on GitHub.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Postman Has Changed Significantly Since 2022: Key Updates Developers Should Know

Postman has undergone major interface and feature changes that render much older documentation and tutorials outdated or inaccurate. The previously separate Tests and Pre-request Script tabs have been consolidated into a single Scripts tab, though the underlying test code remains the same. Postman now offers its own official CLI tool alongside the long-standing Newman runner, while Newman cannot handle the newer v3 YAML collection format introduced in Postman v12. On the CI/CD front, modern Jenkins requires Java 21, and many teams are replacing dedicated Jenkins servers with lightweight GitHub Actions workflows. Postman has also introduced an AI assistant called Postbot that can auto-generate tests, though developers are cautioned to validate generated assertions against specifications rather than assuming current API behaviour is correct.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

EU Cyber Rules Force Industrial Firms to Rethink Legacy Hardware Security Strategies

The convergence of EU regulations including the Cyber Resilience Act, NIS2, and DORA is creating a compliance crisis for organizations running long-established embedded product lines. Many firms already possess technical awareness of their vulnerabilities — such as legacy chips lacking cryptographic isolation — but lack the decision-making frameworks and funding to act on them. Institutional risk-aversion tends to suppress disclosure rather than drive remediation, while capital allocation processes are poorly suited to handling open-ended compliance costs. Manufacturing companies face a particularly acute challenge, as their product lines are tied to long depreciation cycles and capital-intensive supply chains. The paper argues that the transition must be treated as a managed capital process, with interim technical measures used to extend compliant service life rather than forcing abrupt, disruptive overhauls.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Terraform Runner Shut Down the VM It Was Running On Mid-Apply

On July 4, 2026, a DevOps engineer discovered that Atlantis, a Terraform automation tool, destroyed its own runtime environment while applying infrastructure changes. Atlantis was deployed on a k3s virtual machine that was itself managed by the same Terraform stack, creating a circular dependency where the runner controlled the infrastructure it depended on. When a pull request modified the cpu.units attribute on one of the k3s VMs, the bpg/proxmox provider issued a full VM shutdown to apply the change, killing the Atlantis pod mid-execution and losing the apply state. The issue went undetected during planning because Terraform's plan phase does not account for provider-level behaviors like shutdown-before-update, making the hazard invisible until runtime. The problem was resolved by migrating Atlantis from the k3s deployment to a dedicated LXC container that is not managed by the same Terraform stack, breaking the circular dependency entirely.

0 comments Read more at DEV Community