Thanks for your response.
I verified the timestamp.Assuming it was not correct,the server would return an error code 135 which reads “timestamp out of bounds”.
The embedded device pulls the current UTC time from the web and frames it an OAuth header.So,i am sure the timestamp is reasonably accurate.Of course,the time will be off by few seconds since the embedded device has to pull the time stamp and send a request to the server.
I noticed one discrepancy in OAuth header.The following Authorization header is reported by the OAuth tool:
The “Authorization” header framed by the embedded device is little different.The “oauth_signature” is framed after “oauth_version”
Should the order in which header is framed match with that generated by the OAuth tool?
If so,i am surprised how it worked for me till recently with an out of order “Authorization” header.