DocuSign API:“无效签名凭证”使用专属(嵌入式)收件人时出错 [英] DocuSign API: "Invalid Signature Credentials" error using Captive (Embedded) Recipients

查看:103
本文介绍了DocuSign API:“无效签名凭证”使用专属(嵌入式)收件人时出错的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我正在使用基于SOAP的API调用 CreateAndSendEnvelope将信封创建到所需的DocuSign帐户中。

I am using SOAP based API call "CreateAndSendEnvelope" to create an envelope into desired DocuSign account.

当我将收件人添加为专属/嵌入式收件人时,我可以创建信封罚款,但是在为专属收件人请求令牌时,出现错误无效的签名凭证。

When I add recipients as Captive/Embedded recipient(s), I am able to create an envelope fine but while requesting tokens for the captive recipients, I am getting an error "Invalid Signature Credentials".

以下是我对我的DocuSign模拟帐户提出的要求。

Here is my request that I have made against my DocuSign demo account.

POST https://demo.docusign.net/api/3.0/dsapi.asmx HTTP/1.1
Content-Type: text/xml; charset=utf-8
X-DocuSign-Authentication: 
<DocuSignCredentials>
<Username>****</Username>
<Password>*****</Password>
<IntegratorKey>********</IntegratorKey>
</DocuSignCredentials>
VsDebuggerCausalityData:     uIDPo7akWKVLPM1FtqgHGlxmVBgAAAAAh0Xpou1aEkuLAhpZehuVUhAFJ+e2a3JJm4f7e3PmDFMACQAA
SOAPAction: "http://www.docusign.net/API/3.0/RequestRecipientToken"
Host: demo.docusign.net
Content-Length: 1851
Expect: 100-continue
Accept-Encoding: gzip, deflate

<s:Envelope xmlns:s="http://schemas.xmlsoap.org/soap/envelope/">
<s:Body xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"    xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<RequestRecipientToken xmlns="http://www.docusign.net/API/3.0">
    <EnvelopeID>353c8881-feac-4803-b1f9-5248feb04e70</EnvelopeID>
    <ClientUserID>771</ClientUserID>
    <Username>Minal **</Username>
    <Email>*******</Email>
    <AuthenticationAssertion>
    <AssertionID>74ea161d-5dea-4a2c-8ffb-e754beaab660</AssertionID>
    <AuthenticationInstant>2014-06-27T09:17:06.7147424-04:00</AuthenticationInstant>
    <AuthenticationMethod>Password</AuthenticationMethod>
    <SecurityDomain>Request Recipient Token</SecurityDomain>
    </AuthenticationAssertion>
    <ClientURLs>
    <OnSigningComplete>****;event=SignComplete</OnSigningComplete>
    <OnViewingComplete****;event=ViewComplete</OnViewingComplete>
    <OnCancel>*******;event=Cancel</OnCancel>
    <OnDecline>******;event=Decline</OnDecline>
    <OnSessionTimeout>*****;event=Timeout</OnSessionTimeout>
    <OnTTLExpired>*****;event=TTLExpired</OnTTLExpired>
    <OnException>*****;event=Exception</OnException>
    <OnAccessCodeFailed>*****;event=AccessCode</OnAccessCodeFailed>
    <OnIdCheckFailed>*******;event=IDCheck</OnIdCheckFailed>
    </ClientURLs>
    </RequestRecipientToken>
    </s:Body>
    </s:Envelope>


推荐答案

收到错误无效签名凭证的原因是因为使用嵌入式(又称为强制性)收件人时,您需要使用X509证书签署请求。集成在生产中时是必需的,但在演示环境中则不需要证书。

The reason you are receiving the error "Invalid Signature Credentials" is because when using Embedded (aka Captive) recipients you need sign your requests with an X509 certificate. This is required when your integration is in production, but in the demo environment the certificates are not required.

不幸的是,如果您收到此错误,则表明存在一个错误。设置未在您的开发者帐户上启用,这是您需要联系DocuSign支持或您的客户经理解决的问题。

Unfortunately though if you are receiving this error it means that there is a setting or two not enabled on your dev account, and this is something that you need to contact DocuSign support or your account manager to have resolved.

为帮助加快请求速度,我可以告诉您,需要在您的帐户上启用的两个选项都标记为

To possibly help speed the request I can tell you that the two options that need to be enabled on your account are labeled


  • 在会话中

  • 不执行会话证书

  • In Session
  • Don't Enforce In Session Certificate

同时启用这两个功能,您应该可以使用嵌入式收件人。

Once both are enabled you should be able to use Embedded Recipients.

这篇关于DocuSign API:“无效签名凭证”使用专属(嵌入式)收件人时出错的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆