dsh-jumpserver

Configuration

In DSH, open Settings → JumpServer (a standalone section in the left navigation on DeepSeek Harness 0.2.0+). On 0.1.7 hosts it is the JumpServer tab under Settings → Plugins; on 0.1.5 and earlier it is a card under Settings → Plugins.

Configure:

• JumpServer URL: the absolute base URL, for example https://jumpserver.example.com.
• Access Key: create one from the JumpServer web console under your personal API Key list.
• Secret Key: paired with the Access Key above.

The Access Key/Secret Key use DSH's privileged loopback credential RPC — write-only, the stored values are never read back or displayed. The URL is stored in the jumpserver settings namespace as a non-secret field, so it is read back in plaintext and shown in the card for verification.

HTTP and HTTPS both work out of the box — internal deployments without TLS certificates can use an http:// URL with no extra setup. To enforce HTTPS only, disable it in plugin configuration:

allowInsecureHttp: false

The credential reference names default to JUMPSERVER_ACCESS_KEY_ID / JUMPSERVER_ACCESS_KEY_SECRET and can be changed with akRef / skRef in the plugin configuration.

JumpServer permissions

Create the AccessKey under a JumpServer account that only has read access to the assets you want visible to the assistant. Avoid using a super-admin account's key for this integration.