将 gSOAP 用于 VS 2003/C++访问具有 WS-Security 的 SOAP Web 服务？
我们即将开展一个项目，允许只能使用 C++ / VS 2003 扩展的旧平台调用使用 WS-Security 的基于 SOAP 的 Web 服务。
我的 Google 研究表明 gSOAP 可能是最好的方法。
我正在寻找验证和/或替代建议。
We have an upcoming project to allow an old platform that's only extensible with C++ / VS 2003 to call a SOAP-based web service that uses WS-Security.
My Google research indicates that gSOAP could be the best way to go.
I'm looking for validation and/or alternative suggestions.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
我一直在使用 gSoap 和 wsse 插件来实现 WS-Security，在 Windows 和 Linux 的客户端和服务器端都使用签名。这需要一些努力，但效果很好。它也非常快。
它将要求您将 OpenSSL 与您的项目链接。实际上，我在几个版本之前的 wsse 插件中发现了一个错误，该错误涉及直接调用 OpenSSL 进行签名生成和验证。所有错误都涉及泄漏 OpenSSL 结构。 （这些修复已被接受到源代码树中，并且是当前版本的一部分。）
总体而言，开始工作确实并不困难。我在尝试时使用 SoapUI (http://www.soapui.org/) 来解决签名生成问题验证我是否做错了什么或远程端有问题。
如果您在 Apache2 下进行服务器端 WS-Security，则必须坚持使用 gSoap 附带的 mod_gsoap 0.6。我必须对其进行一些修改，因为默认情况下它不会处理 WS-Security。
我相信，但没有做太多调查，有人破坏了 mod_gsoap 0.7，这是 SourceForge 上可用的当前版本。我花了一段时间才弄清楚 0.7 是 apache2 的段错误，所以也许这会减轻你的痛苦。
I've been using gSoap with the wsse plugin for WS-Security using signatures on both the client and server side for both Windows and Linux. It took some doing, but it works well. It is extremely fast too.
It will require you to link OpenSSL with your project. I actually found a bug in the wsse plugin a few releases back that involved direct calls to OpenSSL for signature generation and validation. All of the bugs involved leaking OpenSSL structures. (The fixes were accepted into the source tree and are part of the current release.)
Overall, it really wasn't that difficult to get going. I used SoapUI (http://www.soapui.org/) to troubleshoot the signature generation when trying to validate if I was doing something wrong or the remote end was having issues.
If you're doing server side WS-Security under Apache2, you'll have to stick with the mod_gsoap 0.6 that comes with gSoap. I had to modify it a bit because it won't deal with WS-Security by default.
I believe, but didn't do a lot of investigation, that someone broke mod_gsoap 0.7 that is the current release available at SourceForge. It took me a while to figure out that 0.7 was segfaulting apache2, so maybe this will save you some pain.