It is really hard to answer your question in a short manner, since implementing a full blown OAuth client is not trivial and requires really understanding the OAuth1.0a specification. It is not rocket science but it really requires sorting out all the bits and pieces.
I will attempt to answer your question piecemeal.
What are base strings?
A signature base string in OAuth is built like this:
- Start with the HTTP method of the request your are sending, in upper case. E.g
POST or GET.
- Add an ampersand (
&) character to that
- Add the URL encoded (percent encoded) URL you are calling in your request (do not include parameters here)
- Add yet another ampersand (
&) character here
- Lastly add the URL encoded parameter string
I'll describe how to create the parameter string you need in that last step.
Gather all the parameters included in the request. You'll find them either in the URL as part of the query string and also in the request body when you are POST-ing requests. Say for example that you are POST-ing the parameter parameter1=value1 to the URL http://example.com/?parameter2=value2. That makes two parameters to include.
Now you also have to sum up all the OAuth parameters that are needed for the protocol to be happy. These would lead to a parameter list looking something like this:
oauth_consumer_key=fffffaaaafffaaaffoauth_nonce=aaaaabbbbbcccccaaaaudi2313oauth_signature_method=HMAC-SHA1oauth_timestamp=1319633599oauth_token=bbbbbbbbbfsdfdsdfsfserwerfsddffdsdfoauth_version=1.0parameter1=value1parameter2=value2
All these individual strings need to be lexicographically sorted on the parameter name (alphabetically should suffice), and concatenated into a string. That's your parameter string.
Am I right on the spaces->%20 example?
Yes. You are talking about percent encoding, which also goes by the name of HTTP encoding and URL encoding. http://en.wikipedia.org/wiki/Percent-encoding.
HMAC-SHA1 involves a message and a key, is the consumer secret the message? Is the consumer key the key then?
The message is the signature base string that you created above. And the key is the combination of your consumer secret and your access token secret. So the key should look like this: CONSUMER_SECRET&TOKEN_SECRET (notice the ampersand). In the absolute first request that you do you will not have a token secret yet, then the key is only CONSUMER_SECRET& (again, notice the ampersand).
How to create a signature through the use of the HMAC-SHA1 algorithm.
I fetched this from http://oauth.googlecode.com/svn/code/csharp/OAuthBase.cs and the secrets and the base string are assumed to be available to the code.
Basically feed an HMACSHA1 instance with a key and a message, render that hash and convert it to a base64 string.
HMACSHA1 hmacsha1 = new HMACSHA1();
hmacsha1.Key = Encoding.ASCII.GetBytes(string.Format("{0}&{1}", UrlEncode(consumerSecret), string.IsNullOrEmpty(tokenSecret) ? "" : UrlEncode(tokenSecret)));
byte[] dataBuffer = System.Text.Encoding.ASCII.GetBytes(signatureBaseString);
byte[] hashBytes = hmacsha1.ComputeHash(dataBuffer);
return Convert.ToBase64String(hashBytes);
If I do manage to create the signature, how do I pass these values to Twitter?
You should easily be able to research what an HTTP header is.
But you can choose to add the final result of the parameters and signature to the URL, I think Twitter even accepts them in the request body on some requests. But the preferred way is through the Authorization HTTP header since it allows for clear separation between protocol specific and request specific parameters.
It should look somewhat like this (taken straight from the OAuth 1.0a spec):
Authorization: OAuth realm="Example",
oauth_consumer_key="0685bd9184jfhq22",
oauth_token="ad180jjd733klru7",
oauth_signature_method="HMAC-SHA1",
oauth_signature="wOJIO9A2W5mFwDgiDvZbTSMK%2FPY%3D",
oauth_timestamp="137131200",
oauth_nonce="4572616e48616d6d65724c61686176",
oauth_version="1.0"
