当用于REST和SOAP时,使用标题“ X-DocuSign-Authentication”的选项和格式是什么?

最佳答案

X-DocuSign-Authentication [HTTP HEADER]


最佳做法:在api身份验证标头中使用混淆的用户名和密码
定义:代表权利发送(API)是SOBO。


给定以下值:


用户名== API服务用户==
[email protected]” == USERID
“ cdcd3fc7-2b3c-40d4-98ed-ff90add317ca”
密码==“您的密码” = EncryptedAPIPassword ==
“ / A5hpPhSczID + JNEKZbg5mYf7 + 7 =”
SOBOUser ==“ [email protected]” == USERID
“ eacd3fc7-2b3c-40d4-98ed-ff90add317ff”
Integratorkey ==“ YDMN-339fa93c-fcf0-4390-8141-2e0f071ffa2e”


您的代码需要为HTTP标头生成http标头值
X-DocuSign-身份验证:

XML格式:

非索博

<DocuSignCredentials><Username>cdcd3fc7-2b3c-40d4-98ed-ff90add317ca</Username><Password>/A5hpPhSczID+JNEKZbg5mYf7+7=</Password><IntegratorKey>YDMN-339fa93c-fcf0-4390-8141-2e0f071ffa2e </IntegratorKey></DocuSignCredentials>


索宝

<DocuSignCredentials><Username>cdcd3fc7-2b3c-40d4-98ed-ff90add317ca</Username><Password>/A5hpPhSczID+JNEKZbg5mYf7+7=</Password><IntegratorKey>YDMN-339fa93c-fcf0-4390-8141-2e0f071ffa2e</IntegratorKey><SendOnBehalfOf>eacd3fc7-2b3c-40d4-98ed-ff90add317ff </SendOnBehalfOf></DocuSignCredentials>


JSON格式:

非索博

{"Username":"cdcd3fc7-2b3c-40d4-98ed-ff90add317ca","Password":"/A5hpPhSczID+JNEKZbg5mYf7+7=","IntegratorKey":"YDMN-339fa93c-fcf0-4390-8141-2e0f071ffa2e"}


索宝

{"Username":"cdcd3fc7-2b3c-40d4-98ed-ff90add317ca","Password":"/A5hpPhSczID+JNEKZbg5mYf7+7=","SendOnBehalfOf":"eacd3fc7-2b3c-40d4-98ed-ff90add317ff","IntegratorKey":"YDMN-339fa93c-fcf0-4390-8141-2e0f071ffa2e"}


API服务用户
除非您要创建用户,否则服务帐户不需要是管理员,而是必须具有SOBO和“帐户范围”权限。

SOBO用户
SOBO用户不必是管理员,但必须具有发送权限并成为服务帐户用户帐户中的用户。您仅在执行操作时使用该用户ID,因为该用户喜欢发送或作废。

Here is a link to the full sized Infographic I created to assist with this shown below

rest -  header X-DocuSign-Authentication应该如何用于REST和SOAP?-LMLPHP

09-28 09:59