小编use*_*540的帖子

[最终更新] 根据此线程修复：https://github.com/docusign/docusign-esign-node-client/issues/295

显然与 DocuSign 的 API 的安全添加相关。

今天之前我还没有遇到过这个问题。上周我向客户提供了一个演示，相同的代码运行良好。今天我得到以下信息：

{
    "status": 444,
    "response": {
        "req": {
            "method": "GET",
            "url": "https://demo.docusign.net/restapi...",
            "data": {},
            "headers": {
                "user-agent": "node-superagent/3.8.2",
                "x-docusign-sdk": "Node",
                "authorization": "Bearer ABC...",
                "content-type": "application/json",
                "accept": "application/json"
            }
        },
        "header": {
            "content-type": "text/html",
            "x-docusign-tracetoken": "2eeb8caa-8865-4898-bef9-d3611bfaa3f7",
            "x-docusign-node": "DA2DFE5",
            "date": "Fri, 17 Jun 2022 01:02:02 GMT",
            "content-length": "54",
            "connection": "close",
            "strict-transport-security": "max-age=31536000; includeSubDomains"
        },
        "status": 444,
        "text": "The custom error module does not recognize this error."
    }
}

通过节点 SDK，我使用 获取令牌requestJWTUserToken，并设置 apiclient …