mirror of https://github.com/NVIDIA/OpenShell.git synced 2026-10-14 04:59:28 +08:00

Files

T

History

Krzysztof Malczuk e38d7254e6 fix(policy): reject unknown endpoint security modes (#3187 )

* fix(policy): reject unknown endpoint security modes

Closes #3046

Validate TLS, enforcement, and access values across policy and provider profile ingress, and prevent runtime parsing from falling back to audit for unknown enforcement values.

Signed-off-by: Krzysztof Malczuk <kmalczuk@redhat.com>

* fix(policy)!: use enums for endpoint security modes

Replace the public TLS, enforcement, and access strings with protobuf enums and carry the typed values through policy composition, provider profiles, drivers, and runtime conversion.

Preserve the documented YAML spellings, reject unknown and invalid numeric enum values consistently, and update generated Go bindings, SDK conversions, tests, and policy documentation.

Signed-off-by: Krzysztof Malczuk <kmalczuk@redhat.com>

---------

Signed-off-by: Krzysztof Malczuk <kmalczuk@redhat.com>

2026-09-18 16:48:33 +00:00

src

fix(policy): reject unknown endpoint security modes (#3187 )

2026-09-18 16:48:33 +00:00

Cargo.toml

refactor(providers)!: make provider profiles import-only (#3383 )

2026-09-17 22:59:27 +00:00

README.md

docs(architecture): reset subsystem docs (#1184 )

2026-05-07 08:59:02 -07:00

README.md

openshell-providers

Provider discovery and normalization for credentials that sandboxes need at runtime.

The gateway persists provider records. The sandbox supervisor fetches resolved provider environment from the gateway and injects credentials into agent child processes. This crate keeps provider-specific discovery and normalization logic out of the CLI and gateway control flow.

Responsibilities

Discover local credentials from environment variables and known config files.
Normalize discovered data into provider records.
Keep provider-specific parsing rules in provider modules.
Avoid logging credential values.

Non-Responsibilities

Persisting provider records.
Authorizing provider CRUD operations.
Injecting credentials into sandbox child processes.
Routing inference requests.

Those are owned by the gateway, sandbox supervisor, and router.

Security Notes

Provider data often contains API keys, bearer tokens, or local account configuration. Discovery code should return structured values without printing or tracing secrets. Callers that display provider data must redact sensitive fields by default.