Contributions
Re: Changing the SoapUI 4.5 BinarySecurityToken ValueType
Hi Rao, Turned 'must understand' off and changed the name space and now looks like (based on the http log) SoapUI is sending two sets of wsse:Security tags. Same error on the server side that it doesn't accept X509PKIPathv1 Thanks.6KViews0likes0CommentsRe: Changing the SoapUI 4.5 BinarySecurityToken ValueType
Hi Rao, One way I tried was to right click on the SOAP request and select Outgoing WSS > Apply. I then tried to change the SOAP code as you suggested but the actual SOAP sent in the "http log" is shows SoapUI just forcing the value back to X509PKIPathv1. Was there another way I should try to make this change?6KViews0likes0CommentsChanging the SoapUI 4.5 BinarySecurityToken ValueType
How do you get soapUI 4.5 to send a binary X509 security token as ValueType #X509v3. Currently it is sending as ValueType #X509PKIPathv1. Both types are in the same spec document (p. 8 ) so I assume there must be a way to switch between them. For example <wsse:BinarySecurityToken xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" EncodingType="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-soap-message-security-1.0#Base64Binary" ValueType="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-x509-token-profile-1.0#X509PKIPathv1"> should become <wsse:BinarySecurityToken xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" EncodingType="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-soap-message-security-1.0#Base64Binary" ValueType="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-x509-token-profile-1.0#X509v3">8.9KViews0likes7Comments