hansjone/dsh-im-ops
1
0
Fork 0
mirror of https://github.com/hansjone/dsh-im-ops.git synced 2026-10-15 07:30:48 +08:00
Code Issues Projects Releases Packages Wiki Activity Actions

fix: improve WhatsApp settings and isolate IM host authentication
Some checks are pending
CI / Test, build, and verify package (push) Waiting to run
Details

Browse source
This commit is contained in:
oliver 2026-10-11 17:03:38 +08:00
parent bcbe85fdb1
commit bf73b0c0af
28 changed files with 848 additions and 116 deletions
Download patch file Download diff file Expand all files Collapse all files

2
README.en.md
View file

@ -106,6 +106,8 @@ A GitHub-source installation fetches and builds a Git dependency directly. With
After installation, follow the built-in instructions on each channel page to scan a QR code or enter credentials. Secrets and Tokens are sent only to the local Harness Host and stored through its protected credential provider; status responses and bot lists never return them.
When also using `uds-auth`, install `dsh-im-ops >= 4.9.1-ops.38` and `uds-auth >= 0.2.21`, then restart the Host. IM background calls use the optional `udsAuth.runAsHost()` callback to isolate browser login context. Hosts without that authentication plugin need no additional configuration. Authentication rejections report `HARNESS_LOGIN_REQUIRED` / `HARNESS_ACCESS` and preserve chat bindings. See [Host authentication integration and troubleshooting](docs/host-auth-integration.md).
If this machine must use a forward proxy to reach Feishu, set `HTTPS_PROXY` to a full HTTP proxy URL before starting `dsh web` (for example, `http://proxy:8080`; lowercase `https_proxy` is also supported, with `HTTP_PROXY` accepted as a fallback), then restart the Host after changing it. Feishu registration and credential verification reuse the SDK's proxy-aware HTTP client, while the message WebSocket explicitly uses that proxy; the WebSocket path does not currently read `ALL_PROXY` or `NO_PROXY`.
If this machine cannot reach the Telegram Bot API directly, use Node.js 22.21 or newer and enable Node's environment proxy support before starting `dsh web`: