pgrhome
Occasional Contributor
Joined 12 years ago
User Profile
User Widgets
Contributions
Incorrect values getting passed
I have a .Net WCF service which I am testing with SoapUI version4.6.2. All is working but I have an issue that I just cannot get around at the moment. I am using a password digest which adds a nonce and a created date. The passwordType is set to PasswordDigest. So, when I make the call, these values are populated into the Soap Request as below. <soapenv:Header> <wsse:Security xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd" xmlns:wssu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd"> <wsse:Security xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd" xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd"> <wsse:UsernameToken wsu:Id="UsernameToken-38"><wsse:Username>XXXXXXXXXXX</wsse:Username> <wsse:Password Type="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-username-token-profile-1.0#PasswordDigest">0OLlyLiaAjG+APSRFyHkWl8b5BQ=</wsse:Password> <wsse:Nonce EncodingType="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-soap-message-security-1.0#Base64Binary">wmI0VZSTAmrJ0ELQa7ybcQ==</wsse:Nonce> <wsu:Created>2013-12-09T12:43:13.895Z</wsu:Created> </wsse:UsernameToken> </wsse:Security> <urn:ESBMetaData> <urn:OriginalServiceCallerID>xxxxxxxxxxxxxxxxxxxx</urn:OriginalServiceCallerID> </urn:ESBMetaData> <urn1:ESBContext soapenv:mustUnderstand="1"> <urn1:BusinessContextType>xxxxxxxxxxxxxxxxxxxxxxxxxxxxx</urn1:BusinessContextType> <urn1:BusinessContextInstanceId>uuid:7dc57353-9069-442d-8b69-163f676dd3e3</urn1:BusinessContextInstanceId> <urn1:ServiceRequestId>uuid:7dc57353-9069-442d-8b69-163f676dd3e3</urn1:ServiceRequestId> </urn1:ESBContext> </soapenv:Header> But the values for the password, nonce and created date from with in the .Net WCF service are as follows: Username := XXXXXXXXXXXXXXXXXXXX Password := drke/Qbzob5IY7KzmCBeb6q09ho= Nonce := oZiTJpbiVrranub4F1Sjbw== Created := 2013-12-09T12:43:35.320Z The funny thing is thou, that if I call the service again, I get the following <wsse:Security xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd" xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd"> <wsse:UsernameToken wsu:Id="UsernameToken-39"><wsse:Username>XXXXXXXXXXXXXXXXX</wsse:Username> <wsse:Password Type="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-username-token-profile-1.0#PasswordDigest">drke/Qbzob5IY7KzmCBeb6q09ho=</wsse:Password> <wsse:Nonce EncodingType="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-soap-message-security-1.0#Base64Binary">oZiTJpbiVrranub4F1Sjbw==</wsse:Nonce> <wsu:Created>2013-12-09T12:43:35.320Z</wsu:Created></wsse:UsernameToken></wsse:Security> <urn:ESBMetaData Which as you can see is holding the password and nonce values that the .Net WCF program thought was the original call. Must be something simple, but cannot see it. Any help?941Views0likes0CommentsLine -1: Response is missing or empty
Can anyone explain this message I get when I click on the submit button? I am also getting this message as well. The JVM could not be started. The maximum heap size (-Xmx) might be too large or an antivirus or firewall tool could block the execution. This app was working fine on my box and the antivir/firewall have not been changed. Thanks3.7KViews0likes2CommentsMissing Raw Data
Hello, I am still quite new to this fascinating tool, but I have done something and I don't know how to get it back. Anyway, here goes. Whilst processing a request, after I had submitted the request to an endpoint, if I clicked on the tab called raw, I would see a representation of what was sent over the wire. But now it has stopped working and all I get is the request headers. How do I switch this brilliant functionality back on?35KViews0likes9Comments[Resolved] PasswordDigest
I am using a password digest to create a set of standard headers on a request: <wsse:Security xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd" xmlns:wssu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd"> <wsse:UsernameToken> <wsse:Username>username</wsse:Username> <wsse:Password Type="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-username-token-profile-1.0#PasswordDigest"> weYI3nXd8LjMNVksCKFV8t3rgHh3Rw== </wsse:Password> <wsse:Nonce>WScqanjCEAC4mQoBE07sAQ==</wsse:Nonce> <wssu:Created>2013-04-16T01:24:32Z</wssu:Created> </wsse:UsernameToken> </wsse:Security> Can someone please explain how the Nonce and Password fields are generated? I ask because I have a class that picks these value and then uses them to validate the password field. Currently known values are processed correctly, but when I run this in SoapUI my code fails. Are both the password and Nonce fields just random base64 strings, or are they related in some way?1.6KViews0likes1Comment