WS 安全 Coldfusion
正在处理与 Coldfusion 的 docuSign 集成，并且需要帮助来使用 WS 安全性发出 SOAP 请求。
Working on a docuSign integration with Coldfusion and need assistance in making the SOAP request using WS security.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
您的问题细节有点短，但我认为您的意思是 Web 服务 SOAP 安全扩展。
几年前，当我们与 .NET Web 服务通信时，我们必须这样做。基本思想是提供一组额外的 SOAP 标头，其中包含安全信息，例如：
为此，您需要根据定义的标准创建一个新的 XML 文档 此处。接下来，您需要编写代码来创建 SOAP 标头。这意味着：
创建远程 Web 服务对象，例如
var objWebSvc = createObject("webservice", "http://remoteURL?WSDL");创建 XML 文档来表示新标头
addSOAPRequestHeader()然后当然，如果他们调用您的 Web 服务，您需要从 SOAP 请求中解析出这些标头并验证它们。这可以通过使用 getSOAPRequestHeader() 获取 XML 并解析信息来完成。
我发现这是一项容易出错的任务，而且（基本上）是一种巨大的痛苦。我们集成的 Web 服务最终放弃了这一要求，显然是因为任何尝试连接的非本机 .NET 的 Web 服务都很难实现该规范。
祝你好运！
Your question is a little short on detail, but I presume you mean the Web Services SOAP security extension.
We had to do this a few years back when communicating with a .NET web service. The basic idea is that you provide a set of extra SOAP headers that contains security info such as:
To do this you need to create a new XML document as per the standard defined here. Next you will need to write code to create the SOAP headers. This means:
Create your remote web service object, e.g.
var objWebSvc = createObject("webservice", "http://remoteURL?WSDL");Creating an XML document to represent the new headers
addSOAPRequestHeader()Then of course if and when they call your web service you'll need to parse out those headers from their SOAP request and validate them. That can be done by grabbing the XML using
getSOAPRequestHeader()and parsing out the info.I found this to be an error prone task and (basically) a royal pain. The web service we integrated with eventually dropped the requirement, apparently becuase the any web services trying to connect that were not native .NET were having a hard time implementing the specification.
Good luck!
我不久前在博客上写过这个。看看这是否有帮助：
http://onlineanthony。 blogspot.com/2010/05/using-ws-security-for-soap-in.html
I blogged this a while back. See if this helps:
http://onlineanthony.blogspot.com/2010/05/using-ws-security-for-soap-in.html