FACTUAL ACTIVITY RECORD · An activity record based on work that took place
Restricting production communication from Runner to the broker
Closing the external boundary with a fixed endpoint, short-lived credentials, and strict response checks
Purpose
The production route from Runner to the broker needed to constrain destination, credentials, request size, and response content to prevent bypasses or mismatches.
Implementation
Production allows only one fixed HTTPS endpoint and authenticates with a short-lived runtime identity token. The client rejects redirects, queries, and user information, limits request size and timeout, and validates JSON shape, provider identity, and request hash so it cannot accept a result from another request.
The implementation shows POST to a fixed endpoint, redirect rejection, timeout, schema validation, and binding the response to the request digest. Only the error name is shortened.
Rendering diagram…
What was confirmed
Verification results
Targeted tests passed for endpoint restrictions, short-lived authentication, size and timeout limits, and response binding.
At the cutoff, live communication with the production broker had not been verified.
Basis for completion
The work was complete when Runner-to-broker communication was fixed at the boundary and authentication plus request and response checks passed.