cooper-oai f4275a2a2e Use runtime authentication for remote-control requests (#60073) ...

## Why

Remote-control enrollment, refresh, and client-management requests used ChatGPT bearer authentication without resolving the configured runtime authentication mode.

## What changed

Pass the app server's runtime auth slot and mode into remote control, and resolve authentication and HTTP client policy for each request. Supported OpenAI destinations use fresh runtime assertions in `dual_header` or `assertion_only` mode, while custom destinations retain bearer authentication.

Wait for runtime authentication to initialize and reject unsupported OpenAI origins or mismatched registered accounts. Pairing continues to use its server token.

## Testing

Add transport and app-server integration coverage for both runtime auth modes, fresh assertions, shared runtime registration, network policy enforcement, account validation, redirect credential handling, and pairing token preservation.

GitOrigin-RevId: 5401cf565630ab84eaba71ff6040ac27f7b92461

2026-11-07 06:32:12 +00:00

..

src

Use runtime authentication for remote-control requests (#60073)

2026-11-07 06:32:12 +00:00

BUILD.bazel

app-server: move transport into dedicated crate (#20545)

2026-05-01 09:23:47 -07:00

Cargo.toml

Use runtime authentication for remote-control requests (#60073)

2026-11-07 06:32:12 +00:00