// the find
pzhgugu/OPCUA-Server
一个基于 Java 17、Spring Boot 3 和 Eclipse Milo 的 OPC UA Server。它不是只能在控制台里跑起来的 SDK 示例，而是把 OPC UA 服务、节点管理、端点配置、证书管理、用户认证和运行状态监控一起放进了 Web UI。
A Spring Boot 3 + Eclipse Milo OPC UA server with a browser-based management UI for nodes, certificates, users, and endpoints. Targets industrial engineers who need to ship an OPC UA server without rebuilding it from SDK samples every time. Fills a real gap — most open-source Java OPC UA projects stop at 'it connects'.
The Web UI covering the full management surface (address space, PKI, users, endpoints) in one place is the actual differentiator — Eclipse Milo is fine but its samples are useless for delivery. The Maven profiles (skip-frontend, with-frontend) are a practical build-time split that makes CI and local dev both workable. Full security policy matrix — None through Aes256_Sha256_RsaPss — is wired up out of the box, which saves a week of Milo boilerplate. The public batch-create API (`/public/batch-create-nodes`) is a smart addition for automated provisioning from gateways or scripts.
H2 file database is a hard ceiling for anything beyond a single-node deployment — no clustering, no HA, and file locking under concurrent load is fragile. Default credentials (`admin/admin123`) are documented but the warning to change them in production is easy to miss; a forced password-change flow on first boot would be better than a README note. The OPC UA PKI path (`System.getProperty('java.io.tmpdir')` → `opcua-server/security`) is in the temp directory, meaning a reboot or OS cleanup can wipe your trust store. The `CertificatePersistenceTest.java` file sitting in the service package under `src/main` is a test class that ships in the production jar — that's a packaging mistake.