Summary
Feature request / improvement
openclaw may be deployed inside a trusted internal network where no user authorization is required. At the moment the only viable approach is to enable the trusted proxy option and place nginx in front of the service.
This workaround feels unnecessary and awkward in environments such as Kubernetes. Hardcoding headers in a proxy does not meaningfully improve security, especially when authentication and authorization are already handled by external infrastructure components (API gateways, ingress controllers, service meshes, etc.), which are typically more robust and flexible.
In our case, we already operate behind a gateway, so introducing an additional proxy layer solely to satisfy the trusted proxy requirement adds unnecessary complexity and operational overhead.
It would be helpful if openclaw could support running in a mode suitable for trusted internal environments where authentication is intentionally disabled and security is delegated entirely to external components.
Problem to solve
overcomplicated setup of openclaw in trusted networks
Proposed solution
auth mode = none without any validations
Alternatives considered
No response
Impact
should fix issues when running in docker, k8s and other server like solutions
Evidence/examples
No response
Additional information
No response
Summary
Feature request / improvement
openclaw may be deployed inside a trusted internal network where no user authorization is required. At the moment the only viable approach is to enable the trusted proxy option and place nginx in front of the service.
This workaround feels unnecessary and awkward in environments such as Kubernetes. Hardcoding headers in a proxy does not meaningfully improve security, especially when authentication and authorization are already handled by external infrastructure components (API gateways, ingress controllers, service meshes, etc.), which are typically more robust and flexible.
In our case, we already operate behind a gateway, so introducing an additional proxy layer solely to satisfy the trusted proxy requirement adds unnecessary complexity and operational overhead.
It would be helpful if openclaw could support running in a mode suitable for trusted internal environments where authentication is intentionally disabled and security is delegated entirely to external components.
Problem to solve
overcomplicated setup of openclaw in trusted networks
Proposed solution
auth mode = none without any validations
Alternatives considered
No response
Impact
should fix issues when running in docker, k8s and other server like solutions
Evidence/examples
No response
Additional information
No response