Bug with preauth mechanism and SOAP headers?
I'm not sure if this is a bug, but it seems like unexpected behavior and I cannot figure out when or why it happens.
Most of the time when doing a preauth request via SOAP, we receive a response that contains a SOAP header with the normal refresh/update data. I have one user that in every case, we don't receive any SOAP header in the preauth request. Unfortunately our existing code is expecting a SOAP header in all cases generating some Null Pointer Excpetions (and isn't a header needed to be a proper SOAP packet, even if the header is empty?)
Its simple enough for us to avoid the Null Pointer Exception, but is this a potential problem that might have bigger ramifications if we continue to receive empty headers for this user. Has anyone else seen this? Is this expected behavior?