It sounds like you want to authenticate using a client certificate, not a server certificate as was stated in some of the comments. I had the same issue and was able to write a custom transport for SUDS. Here’s the code that works for me. You’ll need your certificates in PEM format for this to … Read more
try to use url=”file:///path/to/file”
According to this page, you should try running sudo pip-3.2 install suds-jurko. It looks like suds may not have been updated to work with 3.2 whereas suds-jurko has been. Hope this helps! EDIT: From the suds-jurko PyPI page: Lightweight SOAP client (Jurko’s fork). Based on the original ‘suds’ project by Jeff Ortel (jortel at redhat … Read more
SUDS provides some convenience methods to do just that: client.last_sent() client.last_received() These should provide you with what you need. I use them for error logging. The API doc for Client class should have any extra info you need.
While there isn’t a certified standard, if you must use SOAP, Suds is your best choice. Suds can be slow on large WSDLs, and that is something they are working on. In the meantime, if you don’t expect your WSDL to change often, you have two options that can buy you a lot of speed: … Read more
Chicklat with its API provides two examples (see at bottom) for solving this problem. The first signs a certificate using SecurityTokenReference and the second signs a certificate using BinaryTokenReference. You don’t have to rely on this API as it’s subjected to license costs, you can do it but you can use alternative libraries to do … Read more
Depending on the complexity of the service, you could use ladon for the server side and mock up the client by hand until there’s a better solution available. Just call the service with suds (or similar) with logging turned on and note the SOAP wrapping on the request. Use that to wrap your request and … Read more