Getting 401 Not Authorized for some resources

rjkip · 2013-03-25T14:09:02.000Z

I have currently authorized our web application for read/write access:

This application will be able to:

Read Tweets from your timeline.
See who you follow, and follow new people.
Update your profile.
Post Tweets for you.

Does this mean I have achieved application-user authentication?

Accessing the resource “GET account/settings” works fine. However, a resource like “GET statuses/user_timeline” does not, returning a 401 Not Authorized. Isn’t this resource available in a user-context?

mattrogowski · 2013-03-25T14:12:46.000Z

Do you have any code to post?

episod · 2013-03-25T15:09:07.000Z

If you’re getting a HTTP 401 on statuses/user_timeline but not on account/settings, it probably means your OAuth code has an issue around the signing of parameters – usually it’s that the screen_name or id parameter you’re passing in to user_timeline isn’t being considered, sorted, and made part of the OAuth 1.0A signature base string.

rjkip · 2013-03-25T15:47:45.000Z

Thank you @episod, that was the hint I needed. The parameters weren’t included in the signature base string.