Aias00 opened a new issue, #6540: URL: https://github.com/apache/shenyu/issues/6540
## Description `applyUpdate` finds `appAuthDO` by appKey, then conditionally saves `authParam` and `authPath`, and publishes a `CREATE` event built from the *unchanged* entity. It never calls any mapper update, so the DTO's `open`/`enabled`/`phone`/`extInfo`/`userId` are dropped. Worse, the path-save guard uses the **DB** value `appAuthDO.getOpen()` (line 161), while validation (`hasMissingPathsWhenOpen`) uses the **DTO** value `authApplyDTO.getOpen()`. If the DB row has `open=false` and the client applies with `open=true` + paths, validation passes but paths are not saved, and the event carries `open=false`. The `applyCreate` path (built via `AppAuthDO.create(AuthApplyDTO)`) persists all those fields, confirming the asymmetry is a bug. ## Location ``` shenyu-admin/.../service/impl/AppAuthServiceImpl.java:145-178 applyCreate path builds DO via AppAuthDO.create ``` ## Impact Enabling path-level auth via the apply-update flow silently fails; published sync data is stale. ## Suggested fix Persist the changed fields (`appAuthMapper.updateSelective(...)` built from the DTO), and use `authApplyDTO.getOpen()` for the path-save branch. ## Related existing issue(s) #6279 (closed) was about the open/enable toggle UI symptom; this is the underlying persistence gap in `applyUpdate`, distinct. _Identified during the 2026-08-02 audit; full list in [`docs/issue-candidates-2026-08-02.md`](docs/issue-candidates-2026-08-02.md)._ -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
