I'm trying to understand why algorithm for calculation of
oauth_signature does not give me the same result as shown here:
http://dev.twitter.com/pages/xauth
In my case I'm getting signedSK = 'MUYmiobRdoK6s0ZVqo4xQNNO17w='
If I URL encode such result it's still very different from
yUDBrcMMm6ghqBEK
Thank you Tom
I will try your algorithm and compare results.
Quick question: why you do this [str substringToIndex:[str
length]-3] ?
Nikolay Klimchuk
On Sep 13, 2:46 am, Tom van der Woerdt wrote:
> Hi Nikolay,
>
> The first part of your code looks fine. You may, however, like to
Still no luck
With your code I'm gettings exactly the same result
MUYmiobRdoK6s0ZVqo4xQNNO17w=
Something really strange in example here http://dev.twitter.com/pages/xauth
Nikolay Klimchuk
On Sep 13, 7:19 am, Tom van der Woerdt wrote:
> Oh, hehe, good point. That's because my Ba
What algorithm you're using for hmac-sha1 and base64
I'm getting different oauth_signature for the xAuth test example
http://dev.twitter.com/pages/xauth
Nikolay Klimchuk
On Sep 13, 1:01 am, Double K wrote:
> hi, my name is Kim.
> I will make XAuth module. So i need develope
7w=
>
> Looks like you're right :-)
>
> @episod: You should fix that! :-)
>
> Tom
>
> On 9/13/10 8:23 PM, Nikolay Klimchuk wrote:
>
>
>
> > Still no luck
>
> > With your code I'm gettings exactly the same result
> > MUYmiobRdoK6s0ZVqo4xQ
Can somebody recalculate test example from http://dev.twitter.com/pages/xauth
???
I'm looking for oauth_signature parameter
I'm getting different result and it does not make any sense so far
On Sep 13, 2:54 pm, Nikolay Klimchuk wrote:
> Thanks Tom
>
> I feel better now LoL
logical explanation for this
Nikolay Klimchuk
On Sep 15, 12:03 pm, Taylor Singletary
wrote:
> Hi Everyone,
>
> I've revised the xAuth examples athttp://dev.twitter.com/pages/xauth--
> you'll find they should have signatures that are easier to reproduce and was
>
The code I've used is in the first message of this topic
On Sep 16, 12:21 pm, Taylor Singletary
wrote:
> Can you share the code you're using?
>
> On Wed, Sep 15, 2010 at 8:02 PM, Nikolay Klimchuk wrote:
>
>
>
> > That's really puzzling for
Second part of the base string:
oauth_consumer_key=sGNxxnqgZRHUt6NunK3uw&oauth_nonce=WLxsob
j4rhS2xmCbaAeT4aAkRfx4vSHX4OnYpTE77hA&oauth_signature_method=HMAC-
SHA1&oauth_timestamp=1276101652&oauth_version=1.0&x_auth_mode=client_auth&x
_auth_password=
%25&123!aZ+()456242134&x_auth_username=tpFriendl
;t do a thing. I'd say that the issue is at that
> function.
>
> Tom
>
> On Sep 18, 2010, at 11:41 PM, Nikolay Klimchuk wrote:
>
>
>
> > Second part of the base string:
> > oauth_consumer_key=sGNxxnqgZRHUt6NunK3uw&oauth_nonce=WLxsob
> &g
p;";
Gives oauth_signature="1L1oXQmawZAkQ47FHLwcOV%2Bkjwc%3D"
On Sep 16, 12:21 pm, Taylor Singletary
wrote:
> Can you share the code you're using?
>
> On Wed, Sep 15, 2010 at 8:02 PM, Nikolay Klimchuk wrote:
>
>
>
> > That's really puzzling for me. I've
Sorry I don't know answer on your question but in general would be
nice to have more informative error messages from Twitter
I'm tired of Failed to validate oauth signature and token, if there is
a problem with timestamp just let me know!
It will also reduce amount of messages in this group
On S
12 matches
Mail list logo
