You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Require the lease id for provider artifacts after the provider lease ends #4950
#4945 binds leased artifacts and diagnostics records to the lease id that produced them (ADR 0007). One route still serves leased output by tenant only.
Provider artifacts after release.packages/daemon/src/sessions/handlers/lease.ts checks the lease id while the provider lease is active (assertRequestHoldsActiveProviderLease). After release, the provider-session lookup checks only the tenant. Another client with the same proxy token and tenant label can list the cloud artifacts of a released provider session.
Expected: provider artifacts of a leased session require that lease id after release too, as #4945 does for daemon artifacts. Decide where the released lease id is kept (the ended-lease ledger already holds it).
The issue reports existing authorization behavior that is wrong: after a provider lease is released, the provider-session lookup checks only tenant, allowing another client with the same proxy token and tenant to list cloud artifacts. It identifies a concrete route/file and expected fix, so a maintainer can act on it.
Activity
apex-sentinel-staging commentedon Nov 22, 2026
Apex Sentinel · Issue review
Suggested label:
bugThe issue reports existing authorization behavior that is wrong: after a provider lease is released, the provider-session lookup checks only tenant, allowing another client with the same proxy token and tenant to list cloud artifacts. It identifies a concrete route/file and expected fix, so a maintainer can act on it.
Required sections