A client of mine is reporting the following issue. It seems that reporting API requests have ceased working, and my resource believes it be related to the header, as it has been a problem previously. Has there been a change to the way request headers should be configured? Client Care is moving very slowly, so I wanted to post this and see if anyone here had helpful insight for us.
"We are calling omniture api to pull the top bios & shows. Its was working fine with “<wsse:Security xmlns:wsse="http://www.omniture.com" wsse:mustUnderstand="1”>” header until march 8th but now it stopped working, Last november same issue happened and you asked us to change the request header and then it started working. We don’t know what has to be in header now so we tried with old header “<wsse:Security SOAP-ENV:mustUnderstand="1”>” but both are not working. When we use new header then it returns invalid user in response and old header returns empty array. Please find the response screenshots below."