tokens
tokens
¶
Token minting for the per-container gate.
Each task gets a prefixed random 128-bit hex token. The token travels to the container only via the sidecar JSON the supervisor reads; there is no on-disk token registry, and revocation is simply the supervisor's death (the gate stops accepting requests when its process exits).
Token format: terok-g-<32 hex chars> (e.g. terok-g-a1b2c3…).
mint_gate_token()
¶
Generate a fresh 128-bit hex gate token.
Uses secrets.token_hex(16) for cryptographic randomness. The
supervisor validates this single token directly via
_SingleTokenStore,
so there is nothing to persist.