Repository navigation
Description
Situation
This came from agent-filed user feedback. An author wants a private app to expose narrowly scoped product JSON without opening its other routes. The requested boundary permits anonymous GET, HEAD and OPTIONS requests to explicitly declared paths while keeping neighbouring routes authenticated.
Pain
The reporter observed an unauthenticated GET to /api/apps/<appId>/public/... returning HTTP 401 before the app handler runs. No response body was supplied. The reporter left sharing settings and platform access code unchanged.
The denial matches the documented contract. Access control defines app-wide sharing and limits manifest no-auth declarations to the separate public webhook surface. A path component named public has no special meaning.
The mechanism is explicit. isAppApiPathPublic consults api.noAuth only for /api/app-api/<appId>/.... Dashboard-side admission checks only whether the entire app is link-public. Without an accepted session, the remaining verification branches return 401. The edge therefore rejects the request before dispatch. Existing tests expressly require this distinction.
There is a narrower workaround than publishing the entire app. An exact api.noAuth entry can expose /api/app-api/<appId>/public/products while the app remains private. Both URL families dispatch to the same app entrypoint. Despite its webhook-oriented documentation, this surface does not restrict handlers to webhook payloads. Authors must use the alternate URL and enforce allowed methods themselves. The manifest schema accepts only a boolean or path list for noAuth, with no method-scoped grant.
Derived reproduction, not executed:
- Derived from code: Start with an installed private app whose API handler serves a non-reserved
/public/productssub-path. - Derived from code: Declare
api.noAuth: ["/public/products"]and keep app-wide sharing private. - Reporter-provided symptom, concrete path derived from code: Send an anonymous GET through the public edge to
/api/apps/<appId>/public/products. It receives 401 before dispatch. - Derived from code: Request
/api/app-api/<appId>/public/productsinstead. The declaration admits that path, but does not restrict admission by HTTP method.
Header forwarding is a requirement, not a separately established defect. The dispatch route returns the handler response, and cache middleware preserves explicit Cache-Control. Nothing in this path establishes lost CORS or ETag headers.
Version and history: Rome 1.1.194, commit 8a71a43a9f27ab14f86de5cbe852d3190f06a31e, is 40 commits behind inspected main b5aa4ec906b8577ff598c1d7f9ac27feff74989e. The relevant verification, manifest, matching, routing and cache-policy code is unchanged. Searches of open and closed issues and PRs found no matching open duplicate. Related PR #1808 concerned public UI pages, explicitly excluded dashboard data grants, and closed without merging.
Diagnostics show a healthy database and no failed or broken apps among 74 apps. Uptime was 274 seconds after an upgrade from 1.1.193. Relay configuration and email/webchat channels were present, but this decision uses local access policy. Browser, viewport and client route were not supplied. These signals do not explain away the deterministic denial.
Possible directions
- Keep the two URL families separate and document exact
api.noAuthentries for public JSON, with handler-level method checks. This avoids a platform change but leaves read-only enforcement to each app. - Add a distinct, opt-in dashboard API declaration for exact normalized paths and allowed methods. This provides platform enforcement but expands the manifest contract and access-control policy. Do not reinterpret existing
noAuthdeclarations. - Add method-scoped grants only to the existing public API surface. This preserves the current dashboard boundary but requires consumers to use
/api/app-api/....
Any platform direction needs tests for original-request methods, undeclared neighbours, path normalization, reserved core routes, authenticated access and CORS preflight. Preserve handler CORS, cache and ETag headers. The verify endpoint itself is a GET probe, so its method cannot stand in for the original request method.
Triage confidence: high — Documentation, verification code and existing tests explicitly exclude dashboard API paths from api.noAuth, explaining the reported pre-handler 401. The strict manifest schema has no method-scoped declaration, and these paths are unchanged between the reporter build and main. Estimated size: medium.
Source: Rome Cloud user feedback, submitted 2026-11-14T11:20:05.150027Z, build 1.1.194. Analyzed against b5aa4ec906 (main); reporter build commit 8a71a43, 40 commits behind main. Filed automatically by Feedback Triage.
Activity