gpt4 book ai didi

docusignapi - SOAP : RequestRecipientToken - "Invalid Recipient" despite matching from RequestStatus

转载 作者:行者123 更新时间:2023-12-05 03:14:25 24 4
gpt4 key购买 nike

我正在测试嵌入式签名,但遇到了以下错误:

“您指定的收件人不是指定信封的有效收件人”

这适用于一个信封,但现在不适用于第二个。即使他们拥有完全相同的信息。

下面是 RequestStatus 的响应:

     <RequestStatusResponse xmlns="http://www.docusign.net/API/3.0">
<RequestStatusResult>
<RecipientStatuses>
<RecipientStatus>
<Type>Signer</Type>
<Email>PLAT-2445@OUTLOOK.COM</Email>
<UserName>RANDOM GUY</UserName>
<RoutingOrder>1</RoutingOrder>
<Sent>2014-07-07T08:18:19.98</Sent>
<DeclineReason xsi:nil="true"/>
<Status>Sent</Status>
<RecipientIPAddress/>
<ClientUserId>PLAT-2445</ClientUserId>
<CustomFields/>
</RecipientStatus>
</RecipientStatuses>
<EnvelopeID>0f2c122f-cb03-46cb-93cc-f0867c7c46df</EnvelopeID>
</RequestStatusResult>
</RequestStatusResponse>

RequestRecipientToken

    <ns1:RequestRecipientToken>
<ns1:EnvelopeID>0f2c122f-cb03-46cb-93cc-f0867c7c46df</ns1:EnvelopeID>
<ns1:ClientUserID>PLAT-2445</ns1:ClientUserID>
<ns1:Username>RANDOM GUY</ns1:Username>
<ns1:Email>PLAT-2445@OUTLOOK.COM</ns1:Email>
<ns1:AuthenticationAssertion>
<ns1:AssertionID>22b97ae7-c663-4135-8e5d-3c73e7461ffe</ns1:AssertionID>
<ns1:AuthenticationInstant>2014-07-02T10:26:03.245-04:00</ns1:AuthenticationInstant>
<ns1:AuthenticationMethod>Password</ns1:AuthenticationMethod>
<ns1:SecurityDomain>Security.com</ns1:SecurityDomain>
</ns1:AuthenticationAssertion>
<ns1:ClientURLs></ns1:ClientURLs>
</ns1:RequestRecipientToken>

响应RequestRecipientToken

  <soap:Fault>
<faultcode>soap:Client</faultcode>
<faultstring>The recipient you have identified is not a valid recipient of the specified envelope.</faultstring>
<faultactor>https://www.docusign.net/api/3.0/dsapi.asmx</faultactor>
<detail>
<ErrorCode xmlns="missing in Web.Config">123</ErrorCode>
<ErrorReason xmlns="missing in Web.Config">The recipient you have identified is not a valid recipient of the specified envelope.</ErrorReason>
</detail>
</soap:Fault>

最佳答案

我想通了。

根本原因:

我创建了两个具有相同收件人信息的信封。 RecipientToken 用于第一个信封,但在第一个信封签名期间,我采用了我的签名,但我的名字拼写不同。

对于失败的信封,我从 RequestRecipientToken 更新了用户名以匹配我刚刚采用的签名。现在成功了。

解决方案:

我选择在创建信封期间为每个专属收件人使用唯一的 ClientUserId。

关于docusignapi - SOAP : RequestRecipientToken - "Invalid Recipient" despite matching from RequestStatus,我们在Stack Overflow上找到一个类似的问题: https://stackoverflow.com/questions/24617920/

24 4 0
Copyright 2021 - 2024 cfsdn All Rights Reserved 蜀ICP备2022000587号
广告合作:1813099741@qq.com 6ren.com