we39/dsh-jumpserver

简体中文

A DeepSeek Harness plugin for querying and managing JumpServer assets through conversation, authenticated with a JumpServer AccessKeyID/AccessKeySecret pair (HTTP Signature).

Why dsh-jumpserver

• Inspect JumpServer assets, users, accounts, permissions, sessions, command audit logs, user groups, command filters, asset-tree nodes, and RBAC roles/bindings through conversation.
• Manage assets, accounts, users, permissions, user groups, command groups, command filters, asset-tree nodes, and custom RBAC roles/bindings, plus password/MFA/SSH-key resets for users.
• Every write operation triggers a mandatory native user-approval prompt — the model cannot bypass it.
• Secrets, passwords, public keys, MFA secrets, and account passphrases are redacted from read responses before they reach the model.
• Authenticate with JumpServer's native HTTP Signature scheme (hmac-sha256); the AccessKeySecret stays in the local DSH credential store.

Requirements

Component	Supported baseline
Node.js	20.11 or newer
DeepSeek Harness	0.1.2-rc.1
JumpServer	REST API v1 (Access Key authentication)

Installation (for the agent)

For local development, install from the local path:

npm ci
dsh plugin --profile add link:/absolute/path/to/dsh-jumpserver

Once published, install a released, immutable tag whenever possible:

dsh plugin --profile add github:we39/dsh-jumpserver#v<version>

Install the mutable development branch only for testing:

dsh plugin --profile add github:we39/dsh-jumpserver

Restart the selected DSH profile after installation. On Windows, use an absolute link:C:/path/to/dsh-jumpserver path.

Configuration

In DSH Web, open Settings → Plugins → JumpServer asset lookup.

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.

Tools

53 tools (12 read-only / 41 write) across 10 domains. All write tools require native user approval.

Domain	Tools	Scope
Assets	5	assets, details, create/update/delete
Users	7	users, details, create/update/delete, password/MFA/SSH-key reset
Accounts	5	asset accounts, details, create/update/delete
Permissions	5	asset-permission rules, details, create/update/delete
Sessions & Audit	2	terminal sessions, command audit logs
User Groups	5	groups, details, create/update/delete
Command Groups	5	command-pattern groups, details, create/update/delete
Command Filters	5	security filters, details, create/update/delete
Asset Tree	6	nodes, details, create/update/delete, move
RBAC	8	roles, bindings, create/update/delete

See docs/tools.md for the full per-tool reference (name, method, path, description).

Session termination and ticket approval are intentionally out of scope.

Security and data boundaries

• The AccessKeySecret never enters tool arguments, model messages, logs, or Git.
• Account secrets/passphrases and user passwords/public keys/MFA secrets are explicitly excluded from every read tool's output, field by field.
• Authenticated requests reject HTTP redirects to avoid forwarding signed requests to another origin.
• Non-loopback HTTP is disabled by default (see allowInsecureHttp).
• Requests have cooperative cancellation, timeouts, and bounded response sizes.
• Error responses expose only a bounded status/detail description.
• id parameters are validated as JumpServer UUIDs before being placed in a request path, preventing path injection.
• All returned fields (names, addresses, comments, usernames, etc.) are treated as untrusted data, not model instructions.

Development

npm ci
npm run verify

Tests use Node's built-in test runner and mocked JumpServer responses.

Structure

• index.js — generic execution engine + full endpoint catalog + write-approval gateway
• client.js — settings-page form card (slot key jumpserver)
• cordis.patch.yml — bundle patch (insert id jumpserver / name dsh-jumpserver)
• docs/tools.md — full tool reference
• test/index.test.js — node:test unit tests

License

MIT