Hi,

We are setting up, my first time, an Oauth connection with Twitter
from Oracle's Siebel.

But we are consistently getting a 401 unauthorized return when sending
the HTTP Transport Service request (a Siebel utility).

This is what I am doing:

-- Consumer Key and Secret are random test values for sharing. If
anyone could test with these values and confirm my signature output
that would be great :)

oauth_nonce: QP70eNmV5123456GSD1GSz44ddRRjvdfSR
oauth_timestamp: 1294118553
oauth_consumer_key: TestValu31xyz678s
oauth_consumer_secret: TestValu32xyz234a
oauth_signature_method: HMAC-SHA1
oauth_version: 1.0

encoded parameter string:

oauth_consumer_key%3DTestValu31xyz678s%26oauth_nonce
%3DQP70eNmV5123456GSD1GSz44ddRRjvdfSR%26oauth_signature_method%3DHMAC-
SHA1%26oauth_timestamp%3D1294118389%26oauth_version%3D1.0
encoded target string: https%3A%2F%2Fapi.twitter.com%2Foauth
%2Frequest_token

complete base string:

POST&https%3A%2F%2Fapi.twitter.com%2Foauth
%2Frequest_token&oauth_consumer_key%3DTestValu31xyz678s%26oauth_nonce
%3DQP70eNmV5123456GSD1GSz44ddRRjvdfSR%26oauth_signature_method%3DHMAC-
SHA1%26oauth_timestamp%3D1294118389%26oauth_version%3D1.0

signature key: TestValu32xyz234a&

oauth_signature (encoded): yd%2BOcLXp86pfpER58mAy%2FBd%2FLTo%3D

URL string:

https://api.twitter.com/oauth/request_token?oauth_consumer_key%3DTestValu31xyz678s%26oauth_nonce%3DQP70eNmV5123456GSD1GSz44ddRRjvdfSR%26oauth_signature_method%3DHMAC-SHA1%26oauth_timestamp%3D1294118389%26oauth_version%3D1.0%26oauth_signature%3Dyd%2BOcLXp86pfpER58mAy%2FBd%2FLTo%3D

OAuth header:

OAuth oauth_consumer_key="TestValu31xyz678s",
oauth_nonce="QP70eNmV5123456GSD1GSz44ddRRjvdfSR",
oauth_signature_method="HMAC-SHA1", oauth_timestamp="1294118389",
oauth_version="1.0", oauth_signature="yd%2BOcLXp86pfpER58mAy%2FBd%2FLTo
%3D"

This header sendt towards: http://api.twitter.com/oauth/request_token

Gives the following result (not the same timestamp as example above):

*** HTTP Transport Parameters:

Request URL = https://api.twitter.com/oauth/request_token
Request Method = POST
Timeout secs = 120000

XML document will be generated with 'UTF-8' character encoding

Sending Request

*** HTTP request Headers for Data Send Request:

User-Agent: Mozilla/4.0
Accept: text/*
Content-Type: application/x-www-form-urlencoded;charset=UTF-8

Authorization: OAuth oauth_consumer_key="TestValu31xyz678s",
oauth_nonce="QP70eNmV5123456GSD1GSz44ddRRjvdfSR",
oauth_signature_method="HMAC-SHA1", oauth_timestamp="1294118553",
oauth_version="1.0", oauth_signature="D3uVyQ7oghvpCagAXao2GavJP0Y%3D"

*** HTTP response Headers from Data Send request:

HTTP/1.1 401 Unauthorized
Date: Tue, 04 Jan 2011 06:22:34 GMT
Server: hi
Status: 401 Unauthorized
X-Transaction: 1294122154-62378-47009
Last-Modified: Tue, 04 Jan 2011 06:22:34 GMT
X-Runtime: 0.01048

Content-Type: text/html; charset=utf-8
Content-Length: 44
Pragma: no-cache
X-Revision: DEV

Expires: Tue, 31 Mar 1981 05:00:00 GMT

Cache-Control: no-cache, no-store, must-revalidate, pre-check=0, post-
check=0
Set-Cookie: k=138.62.0.20.1294122154201712; path=/; expires=Tue, 11-
Jan-11 06:22:34 GMT; domain=.twitter.com
Set-Cookie: guest_id=12941221542108965; path=/; expires=Thu, 03 Feb
2011 06:22:34 GMT
Set-Cookie: _twitter_sess=######; domain=.twitter.com; path=/

Vary: Accept-Encoding
Connection: close

*** HTTP response Body from Data Send request:

Regards,
Thomas Husvæg

-- 
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
http://groups.google.com/group/twitter-development-talk

Reply via email to