In contrast to what the documentation states, the SOAPShim always
encodes the usernameassword in the authorization header.
In our case we make a authentication call to get an token ; the
Authorization header is Basic usernameassword.
The result is a XML with an element <Token> which we need to sent with
any actual user modification.
So we need to send an Authorization header : OAUTH XXXXXXXXXXXXXXXXXX.
The problem is that this header is getting B64 encoded as well, which it
(It is not possible to decode the token first, for it is a string not a
B64 coded string).
As far as i can see, it is not possible to use tokens whithin the
authorization headers in any way.

Does anybody know how to work around this behaviour, we're a bit stuck

Thx in advance

dvandermaas's Profile:
View this thread: