Oauth; Differences in Content from Postman?
I am doing oauth api testing and using postman I can do all the calls successfully. However when I try to utilize SoapUIPro 4.6.4 the requests, they fail for invalid token. I am using the Twitter exa...
Forum Discussion
Ok I am revisiting this issue, I see that the latest version of SoapUIPro (5.1.1) contained a fix for the RequestFilter.filter.request event. So I ran a basic OAuth test and i was pleased to see the header appended to the request, however I note that I have a new error "Receiving response: HTTP/1.1 401 Invalid timestamp 0. Exceeds configured time to live 00:15:00."
So I did a side by side compare of the OAuth headers values:
The string produced by Soap is:
oauth_consumer_key="6E65A733-B50B-4BAF-A15F-XXXXXXXXXXXX", oauth_nonce="-3337028399705576308", oauth_signature="TMuDrjeiH0mab%2FPCUehZtBJ65WI%3D", oauth_signature_method="HMAC-SHA1", oauth_timestamp="1406739280", oauth_token="a166bbd7-3145-4c47-b0d3-dd0c707db047", oauth_version="1.0"
The string produced by Postman is:
oauth_consumer_key="6E65A733-B50B-4BAF-A15F-XXXXXXXXXXXX",oauth_token="ca2340d3-3af5-4c0a-990a-15e4cd8ca856",oauth_signature_method="HMAC-SHA1",oauth_timestamp="1406739431",oauth_nonce="TfZ051",oauth_version="1.0",oauth_signature="IbrcWa1G%2B1nWy%2BDtC9or6v7d4g8%3D"
Both strings have seemly valid values, and do contain a value for time stamp, but they do have two differences in format. The pattern of the data is different, and the soap string contains spaces after the comma prior to each new value. I don't know if that is the actual cause for the host failing to find the value for "timestamp" but i was wondering if there is a method of removing the spaces or altering the data format.
Thanks,
Mark
So I did a side by side compare of the OAuth headers values:
The string produced by Soap is:
oauth_consumer_key="6E65A733-B50B-4BAF-A15F-XXXXXXXXXXXX", oauth_nonce="-3337028399705576308", oauth_signature="TMuDrjeiH0mab%2FPCUehZtBJ65WI%3D", oauth_signature_method="HMAC-SHA1", oauth_timestamp="1406739280", oauth_token="a166bbd7-3145-4c47-b0d3-dd0c707db047", oauth_version="1.0"
The string produced by Postman is:
oauth_consumer_key="6E65A733-B50B-4BAF-A15F-XXXXXXXXXXXX",oauth_token="ca2340d3-3af5-4c0a-990a-15e4cd8ca856",oauth_signature_method="HMAC-SHA1",oauth_timestamp="1406739431",oauth_nonce="TfZ051",oauth_version="1.0",oauth_signature="IbrcWa1G%2B1nWy%2BDtC9or6v7d4g8%3D"
Both strings have seemly valid values, and do contain a value for time stamp, but they do have two differences in format. The pattern of the data is different, and the soap string contains spaces after the comma prior to each new value. I don't know if that is the actual cause for the host failing to find the value for "timestamp" but i was wondering if there is a method of removing the spaces or altering the data format.
Thanks,
Mark