Bound Trino spooling URLs by signing-credential lifetime
Calculate a spool URL's usable delivery window from the earlier of URL and signing-credential expiry. Include delivery delays when reporting the time left to the client, and keep raw tokens out of the record.
Advertised TTL and effective validity
A signed URL’s effective lifetime ends at the earlier of URL expiry and signing-credential expiry. Truthound Core can compare prepared lifetime boundaries before an export promises a download deadline. [1, 2, 3]
ExpiredToken before segment expiry
Trino issue #31856 reports spooling STORAGE with WEB_IDENTITY returning ExpiredToken while advertised segment TTL remains. The source’s production observation and proposed refresh policy are distinct. Follow-up discussion adds that output-buffer delay can consume URI lifetime before delivery. [1]
Record boundaries without secrets
Record nonsensitive signing time, URL expiry, credential expiry, and required fetch deadline. Compute the earlier boundary and compare it with the promised deadline. Keep tokens and credential values out of the table. [1, 3]
A 30-minute promise with 5 minutes
Declare a 30-minute download promise and URL TTL of 30 minutes. With only 5 credential minutes remaining, min(30,5)=5 minutes fails. Effective lifetime 30 minutes passes the time condition. The promise must also account for delay before the client receives the URL. [1, 3]
Compare time without renewing secrets
ColumnPairValidator in Truthound Core Python SDK 3.3.2 compares prepared non-null effective lifetime>=required lifetime in minutes. The operator supplies accurate boundaries. The SDK does not refresh credentials, sign URLs, or guarantee network and IAM success. [1, 2, 3]
Use actual session duration
Review supported pre-signer refresh settings against actual session duration and segment TTL, then test exports near expiry. A time-bound pass still leaves object existence, permissions, and download duration to separate checks. [1, 3]
Advertise the client’s usable window
Advertise only the usable window the client actually receives. Distinguishing configured TTL from effective validity makes bursts of apparently early expiration explainable without exposing secret material. [1, 3]
Application conditions
Prepare nonsensitive signing/URI/credential expiry and fetch deadline records.
Alternatives
Verify supported refresh settings for actual session duration and near-expiry exports.
Limitations
A time-bound pass guarantees neither IAM/network/object existence nor download completion.
Evidence
- Event checked
- Subject checked
- Modified
