thatsthat
2 years agoContributor
After upgrade to ReadyAPI 3.4.6 all of my requests are failing as security header is no longer sent
Strangest issue.
I upgraded to ReadyAPI 3.4.6 ( Build Date: 2023-05-11T09:29:01Z(1) 133f67b0fdcf5ba2d9e5ef029887969c5d7e454d) today.
I have about 2000 API requests pointing to my company's API ...and they all fail now where they working minutes before on the previous version.
I loaded up a copy of Soap UI .. the same requests work fine in that application.
I traced it down to the fact that the wsse:Security header entry (the portion below) is no longer being sent when I make requests .. hence why my server keeps returning 'Invalid Password' .. is there a setting in the Preferences that may have been alterred during upgrade?
<soapenv:Header><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" soapenv:mustUnderstand="1"><wsu:Timestamp wsu:Id="TS-27295C8A48F4535CD416844900173494"><wsu:Created>2023-05-19T09:53:37Z</wsu:Created><wsu:Expires>2023-05-19T09:58:37Z</wsu:Expires></wsu:Timestamp><wsse:UsernameToken wsu:Id="UsernameToken-27295C8A48F4535CD416844900173493"><wsse:Username>voyagefr*xml</wsse:Username><wsse:Password Type="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-username-token-profile-1.0#PasswordDigest">CJC6te4IDurZ0iuBNQrMC61YAJ0=</wsse:Password><wsse:Nonce EncodingType="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-soap-message-security-1.0#Base64Binary">23PO9w4F3jqveObVUcMDlw==</wsse:Nonce><wsu:Created>2023-05-19T09:53:37.349Z</wsu:Created></wsse:UsernameToken></wsse:Security></soapenv:Header> |