DocuSign嵌入式签名returnUrl长度限制? [英] DocuSign embedded signing returnUrl length limit?

查看:73
本文介绍了DocuSign嵌入式签名returnUrl长度限制?的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

在进行DocuSign嵌入式签名过程(过去一直有效)的过程中,我注意到在对文档签名后,'returnUrl'中缺少'event'参数,我被发送回去。



returnUrl如下:

  http://www.example.com/ index.php?param1 = value1 ...& param10 = value10 

正在传递参数从签名返回,但未添加 event = signing_complete 参数。我尝试删除参数,然后突然返回了 event 参数。



进一步试验后,我发现 returnUrl 参数具有500个字符的限制。 还将从 returnUrl 的末尾截断 event 参数。 / p>

DocuSign REST API文档( https://www.docusign.com/p/RESTAPIGuide/Content/REST%20API%20References/Post%20Recipient%20View.htm )。



那么,这是功能还是错误?除了使用会话或数据库存储以外,是否建议使用500个字符的限制?

解决方案

可能存在一些限制到Web服务器本身传递的URL。我没有看到很多人达到这个极限,因为大概大多数时候人们不会在返回URL中输入太多信息。



如果您来自软件具有会话状态的您可以使用以下技术:
1)将您以前通过URL发送的信息添加到字典或集合对象中,并将其保存在服务器上的会话中。遵循该最佳安全做法,以使该信息不容易访问(在URL中而不是所有位置,都很难访问此信息(有关如何正确执行此操作的材料很多,而且可能超出了答案)
2)键和值只是提供您集合的键。
3)从DocuSign返回后,查找对象并检索传递的信息。



如果软件中没有状态,则可以尝试使用其他属性信封的位置以放置其他信息,例如信封自定义字段。您可以在创建时填充这些内容,并且可以在控件返回软件时取回信息。这是有关自定义字段的文章: https://www.docusign.com/p/RESTAPIGuide/RESTAPIGuide.htm#REST API参考/获取信封自定义字段Information.htm


While working on a DocuSign embedded signing process (which has worked in the past), I noticed that after signing the document the 'event' parameter was missing from the 'returnUrl' I was being sent back to.

The returnUrl looks like:

http://www.example.com/index.php?param1=value1 ... &param10=value10

The parameters were being passed on returning from signing, but no event=signing_complete parameter was being added. I tried removing the parameters, and suddenly the event parameter returned.

After further experimentation, I discovered that the returnUrl parameter has a 500 character limit. Anything more is truncated. This will also truncate the event parameter from the end of the returnUrl.

This does not seem to documented in the DocuSign REST API documentation (https://www.docusign.com/p/RESTAPIGuide/Content/REST%20API%20References/Post%20Recipient%20View.htm).

So, is this a feature or a bug? Other than using session or database storage, is there a recommended workaround for the 500-character limit?

解决方案

There might be some limits to the URL that is being passed in by the web servers themselves. I have not seen a lot of people hit this limit because probably most of the time folks do not put that much information into a return URL.

If you are coming from software that has session state you can use the following technique: 1) add the information you were previously sending via URL to a dictionary or a collection object and save it in the session on the server. Follow the best security practices for that one so that this information can't be easily accessed (there is a ton of material on how to do this properly and it's probably beyond this answer) 2) in the url instead of all the keys and values just provide the key to your collection. 3) upon return from DocuSign look up the object and retrieve the passed in information.

If there is no state in your software you can try using other properties of the envelope to put the additional information such as envelope custom fields. You can populate those on create and you can retrieve the information back when the control comes back to your software. Here is the article about custom fields: https://www.docusign.com/p/RESTAPIGuide/RESTAPIGuide.htm#REST API References/Get Envelope Custom Field Information.htm

这篇关于DocuSign嵌入式签名returnUrl长度限制?的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

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