mirror of
https://github.com/openai/codex.git
synced 2026-11-03 19:53:25 +00:00
alexsong-oai
fe52d795c9
## What changed Support `model_providers.amazon-bedrock.aws.credential_export` with `command`, `args`, and `timeout_ms` to supply SigV4 signing credentials from a command's JSON output. Accept both flat credential-process output and nested STS `Credentials` objects. Cache credentials in memory, refresh before expiration, and share exports across sessions with matching AWS configuration. On recoverable authentication failures, run the optional `aws.auth_refresh` command before exporting fresh credentials, coalescing concurrent recovery attempts. Bound command execution time and output size, and keep credential values out of errors. Reject combining `aws.credential_export` with `aws.profile`. Bedrock setup and login reject changes while an exporter is configured, preserving configuration and saved credentials. ## Testing Add coverage for output formats, expiration, credential precedence, caching, concurrent recovery, command failures, and secret redaction. Integration tests verify request signing with rotated credentials, bounded recovery attempts, and setup/login rejection across configuration layers. GitOrigin-RevId: 4ef799f88ab5e3b2578f8f41a5e56e4f30e2cd81
41 lines
2.1 KiB
Markdown
41 lines
2.1 KiB
Markdown
# User verification cancellation (experimental)
|
|
|
|
Local UI clients can cancel a native user-verification RPC by sending
|
|
`userVerification/cancel` with `{requestId}` and the `experimentalApi` opt-in.
|
|
The result is an empty acknowledgment (`{}`). This API does not enable desktop
|
|
verification capability advertisement.
|
|
|
|
`requestId` is the original status, enroll, delete, or verify RPC's string or
|
|
integer ID on the same connection, not the server elicitation ID. Use fresh IDs
|
|
for each operation and a distinct ID for the cancel RPC. Unknown, finished,
|
|
unrelated, and other-connection requests are no-ops.
|
|
|
|
The acknowledgment confirms the cancellation signal without waiting for the OS
|
|
prompt to close. The original RPC completes independently, with
|
|
`cancelled/interrupted` when cancellation prevents completion. Cancellation
|
|
cannot roll back completed effects. It remains effective while a proof waits for
|
|
outbound queue capacity, but cannot retract a response already enqueued.
|
|
|
|
Canceling or resolving an elicitation does not itself stop a separate
|
|
`userVerification/verify` RPC. Clients must cancel that RPC separately and discard
|
|
late proofs after the approval is canceled or resolved. Only one native worker
|
|
runs per app-server; if an OS call remains active after cancellation or timeout,
|
|
subsequent local operations return `failed/providerError` until that worker exits.
|
|
|
|
# Thread removal
|
|
|
|
`thread/archive` and `thread/delete` reject attempts to remove a live internal
|
|
worker with JSON-RPC error `-32600`. The worker's owner controls its shutdown.
|
|
For example, a Guardian reviewer remains available to its parent conversation
|
|
after a client tries to archive or delete it.
|
|
|
|
After the owner releases the worker, its saved conversation can be archived or
|
|
deleted normally. Ordinary client-controlled threads keep their existing behavior.
|
|
|
|
# Amazon Bedrock authentication
|
|
|
|
If `model_providers.amazon-bedrock.aws.credential_export` is configured, Bedrock setup and
|
|
Bedrock login return an error without changing configuration or saved credentials. Remove the
|
|
exporter configuration before selecting another credential source. `aws.credential_export` and
|
|
`aws.profile` cannot be configured together.
|