luawig/dsh-cloudflare-access
Re-validates Cloudflare Access JWTs at the DSH origin so remote Settings, credentials and model discovery work safely.
Solves the gap between "Cloudflare Access protects the hostname" and "DSH itself trusts the request". It re-validates the Access JWT at the DSH origin, so Settings, Credentials, agent-preset management and model discovery can be used from a remote hostname such as https://dsh.example.com without DSH's own ?token= workaround. Ordinary non-privileged remote APIs are governed separately by DSH_CF_ACCESS_ORDINARY_MODE (off, optional, required), while Host and Origin checks always run first and loopback ignores the ordinary policy entirely. In production you pin the team domain and audience through environment variables, and the README notes the security consequence: if a variable exists, even as an empty string, that field is locked and cannot be retargeted from a remote Settings session. The security model is worth reading before deployment — the README is explicit that installing this plugin is not a reason to put DSH on the public internet, and logs record failure categories only, never tokens.
Install
dsh plugin --profile web add dsh-cloudflare-accessThe npm line from the README's Install section, for a Web profile; a github:Luawig/dsh-cloudflare-access form is documented too, and the git tree ships prebuilt lib/index.js and lib/client.js so that route needs no TypeScript or esbuild. Remove with dsh plugin --profile web remove dsh-cloudflare-access. The README's quick start is three steps and the package is only step two: pin --trusted-host to the public hostname first, install and restart, then keep the origin reachable only from Cloudflare.
Compatibility
Version compatibility is the first thing to check, and the README states it in a compatibility matrix: plugin 2.0.x targets DeepSeek Harness 0.1.5-alpha.1 and was live-tested on a Web profile behind Cloudflare Access, while the 1.0.x line predates DSH 0.1.2 and is not compatible with it. The README warns not to assume other DSH releases work until that matrix is updated. Scope is deliberate: this plugin does not replace Cloudflare Access and ships no login page, password store, MFA, session table or Cloudflare API client — identity stays in Access, and only the Cf-Access-Jwt-Assertion header is read. Loopback does not require a JWT, so an SSH tunnel to localhost keeps working, and privileged remote APIs always require one.
Details
- Repo: luawig/dsh-cloudflare-access
- Category: Infrastructure & Deployment
- Stars: 2
- Version: 2.0.0 (npm)
Alternatives
mathangler/dsh-remote-access · kk99668/dsh-mobile-access · harryopo/dsh-cloud-workspaces