DocuSign演示:在签署文档后出现错误“不支持此身份验证模式:NONE”

huangapple go评论72阅读模式
英文:

DocuSign Demo: Error "This authentication mode is not supported: NONE" after signing a document

问题

We will soon start a project using DocuSign APIs from Salesforce. Currently running some proof of concept to test signature with sample document.

The JWT authentication works well but when trying to create an enveloppe to perform a test signature with Demo Docusign org, getting error: "This authentication mode is not supported: NONE". This error occurred both when recipient is an external or an internal docusign user email address.

Followed this documentation: https://developers.docusign.com/docs/esign-rest-api/reference/envelopes/envelopes/create/

Here's the sample request sent:

{
"emailSubject": "Please sign this document",
"documents": [
{
"documentBase64": "dGVzdCBkb2M=",
"name": "Lorem Ipsum",
"fileExtension": "txt",
"documentId": "1"
}
],
"recipients": {
"signers": [
{
"email": "email@add.com",
"name": "Contact Name",
"recipientId": "1",
"tabs": {
"signHereTabs": [
{
"documentId": "1",
"name": "SignHereTab",
"pageNumber": "1",
"recipientId": "1",
"tabLabel": "SignHereTab",
"xPosition": "75",
"yPosition": "572"
}
]
}
}
]
},
"status": "sent"
}

Any idea what can be the cause of the authentication mode error?

Answers provided in this similar question did not help:
https://stackoverflow.com/questions/72966631/docusign-this-authentication-mode-is-not-supported-none-when-trying-to-finis

Tried to add a signatureProviderName but webservice request itself fails

"recipientSignatureProviders": [{ "signatureProviderName": "UniversalSignaturePen_ImageOnly" }]

Error: The signature provider name specified is not valid. Invalid signature provider name: UniversalSignaturePen_ImageOnly

Adding identityVerification via phone number in request eliminates the error, but we were told that phone sms verification should not be mandatory in all requests.

英文:

We will soon start a project using DocuSign APIs from Salesforce.
Currently running some proof of concept to test signature with sample document.

The JWT authentication works well but when trying to create an enveloppe to perform a test signature with Demo Docusign org, getting error : "This authentication mode is not supported: NONE"
This error occurred both when recipient is an external or an internal docusign user email address.

Followed this documentation : https://developers.docusign.com/docs/esign-rest-api/reference/envelopes/envelopes/create/

Here's the sample request sent :

{
	"emailSubject": "Please sign this document",
	"documents": [
		{
			"documentBase64": "dGVzdCBkb2M=",
			"name": "Lorem Ipsum",
			"fileExtension": "txt",
			"documentId": "1"
		}
	],
	"recipients": {
		"signers": [
			{
				"email": "email@add.com",
				"name": "Contact Name",
				"recipientId": "1",
				"tabs": {
					"signHereTabs": [
						{
							"documentId": "1",
							"name": "SignHereTab",
							"pageNumber": "1",
							"recipientId": "1",
							"tabLabel": "SignHereTab",
							"xPosition": "75",
							"yPosition": "572"
						}
					]
				}
			}
		]
	},
	"status": "sent"
}

Any idea what can be the cause of the authentication mode error ?

Answers provided in this similar question did not help:
https://stackoverflow.com/questions/72966631/docusign-this-authentication-mode-is-not-supported-none-when-trying-to-finis

Tried to add a signatureProviderName but webservice request itself fails

"recipientSignatureProviders": [{ "signatureProviderName": "UniversalSignaturePen_ImageOnly" }] 

Error : The signature provider name specified is not valid. Invalid signature provider name: UniversalSignaturePen_ImageOnly

Adding identityVerification via phone number in request eliminates the error, but we were told that phone sms verification should not be mandatory in all requests.

答案1

得分: 1

Does your account have the global setting for requiring all envelope recipients to be authenticated enabled? That would then flow over to API calls as well. Check the "Security Settings" in your Admin settings page for this and if it is enabled, you'd need to disable it.

英文:

Does your account have the global setting for requiring all envelope recipients to be authenticated enabled? That would then flow over to API calls as well. Check the "Security Settings" in your Admin settings page for this and if it is enabled, you'd need to disable it.

答案2

得分: 0

根据与DocuSign支持团队的记录,错误的根本原因是帐户上启用了电子印章,但未启用数字签名。

以下是来自支持团队的回复:

此错误是由于帐户上启用了电子印章而未启用数字签名所导致的。为解决此问题,我将需要在帐户上启用DS电子签名类型。由于这将是此帐户上唯一可用的签名类型,它将默认应用于从此帐户发送的所有信封。用户在创建信封时无需选择它。

在支持团队在内部设置中启用了DS电子签名类型后,这个问题得到了解决,不再需要在通过API创建信封时发送“identityVerification”。

英文:

Following a case logged with DocuSign support, the root cause of the error is electronic seal is enabled on the account and no digital signatures are enabled.

Here's response from support:

> This error is occurring due to the fact electronic seal is enabled on the account and no digital signatures are enabled. To resolve this issue, I will need to enable the DS Electronic signature type on the account. As this will be the only signature available on this account, it will be applied by default to all envelopes sent from this account. Users won't need to select it when creating envelopes.

After support enabled DS Electronic signature type in the internal settings, this resolved the error and no need to send identityVerification when creating enveloppe via APIs

huangapple
  • 本文由 发表于 2023年4月13日 22:45:36
  • 转载请务必保留本文链接:https://go.coder-hub.com/76006817.html
匿名

发表评论

匿名网友

:?: :razz: :sad: :evil: :!: :smile: :oops: :grin: :eek: :shock: :???: :cool: :lol: :mad: :twisted: :roll: :wink: :idea: :arrow: :neutral: :cry: :mrgreen:

确定