Re: [twitter-dev] Re: Missing oauth_verifier
If anyone has questions about the TwitterOAuth library feel free to contact me. Abraham - Abraham Williams | Hacker Advocate | http://abrah.am @abraham | http://projects.abrah.am | http://blog.abrah.am This email is: [ ] shareable [x] ask first [ ] private. On Tue, Sep 7, 2010 at 09:39, G wrote: > For those having issues with the oauth-php library I would suggest > moving to the twitteroauth library found here. > http://github.com/abraham/twitteroauth > It is far simpler and built specifically around the twitter oauth > framework. The oauth-php library I'm sure can do the job, but not > without many hours of work digging through a massive library. > > > > On Sep 6, 5:49 pm, G wrote: > > Your questions helped me find the issue. I'm using oauth-php and > > apparently what I'm doing isn't properly setting the callback URL. > > I'll look for the oauth_callback_confirmed flag for my error checking. > > > > Thanks for the help! > > > > On Sep 6, 4:11 pm, Taylor Singletary > > wrote: > > > > > > > > > Can you share as much information about your request token step as > > > possible? This is the only step you should ever provide a callback URL > > > in. > > > > > Can you verify that you are usinghttp://api.twitter.com/oauth/*for > > > all paths in this sequence. > > > What is the value of oauth_callback on your request token step? Is > > > this the only step that you are you providing this data? Are you > > > presenting this via a query string parameter, an authorization header, > > > a POST body, or any intermingling of the three? > > > > > When you receive your response to request_token, do you get a > > > parameter that indicates oauth_callback_confirmed=true? > > > > > Thanks, > > > Taylor > > > > > On Mon, Sep 6, 2010 at 2:49 PM, G wrote: > > > > I will admit I'm not experienced with oauth at all and maybe I'm > > > > sending bad data in the initial step. I fail to see why I would get > an > > > > appropriate request_token if that were the case though. > > > > > > On Sep 6, 3:42 pm, Tom van der Woerdt wrote: > > > >> Strange, you aren't the first one who reported this. I really think > that > > > >> this behavior should be investigated. > > > > > >> Tom > > > > > >> On 9/6/10 11:23 PM, G wrote: > > > > > >> > I'm not receiving an oauth_verifier key/value pair in after the > user > > > >> > grants access through my app. > > > > > >> > I'm receiving the at the URL specified in my app settings and in > my > > > >> > initial token request. The callback I'm getting looks like this > > > > > >> > > http://callback_url?oauth_token=xHddBl5uYQnSIESC4P16bmWS3ObDgMroXglEQ... > > > > > >> > Every issue I have seen regarding this has to do with not > supplying > > > >> > callback url's. I have included them in every step. I have even > tried > > > >> > to use it when asking for user authorization which the tutorial > here: > > > >> >http://dev.twitter.com/pages/authsaysIdon't need. I'm really at a > > > >> > loss. > > > > > >> > I have tried to use the PIN method as well, but again the above > > > >> > tutorial falls short at the critical step of what to do when the > PIN > > > >> > is aquired. > > > > > > -- > > > > 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?hl=en > > -- > 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?hl=en > -- 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?hl=en
[twitter-dev] Re: Missing oauth_verifier
For those having issues with the oauth-php library I would suggest moving to the twitteroauth library found here. http://github.com/abraham/twitteroauth It is far simpler and built specifically around the twitter oauth framework. The oauth-php library I'm sure can do the job, but not without many hours of work digging through a massive library. On Sep 6, 5:49 pm, G wrote: > Your questions helped me find the issue. I'm using oauth-php and > apparently what I'm doing isn't properly setting the callback URL. > I'll look for the oauth_callback_confirmed flag for my error checking. > > Thanks for the help! > > On Sep 6, 4:11 pm, Taylor Singletary > wrote: > > > > > Can you share as much information about your request token step as > > possible? This is the only step you should ever provide a callback URL > > in. > > > Can you verify that you are usinghttp://api.twitter.com/oauth/*for > > all paths in this sequence. > > What is the value of oauth_callback on your request token step? Is > > this the only step that you are you providing this data? Are you > > presenting this via a query string parameter, an authorization header, > > a POST body, or any intermingling of the three? > > > When you receive your response to request_token, do you get a > > parameter that indicates oauth_callback_confirmed=true? > > > Thanks, > > Taylor > > > On Mon, Sep 6, 2010 at 2:49 PM, G wrote: > > > I will admit I'm not experienced with oauth at all and maybe I'm > > > sending bad data in the initial step. I fail to see why I would get an > > > appropriate request_token if that were the case though. > > > > On Sep 6, 3:42 pm, Tom van der Woerdt wrote: > > >> Strange, you aren't the first one who reported this. I really think that > > >> this behavior should be investigated. > > > >> Tom > > > >> On 9/6/10 11:23 PM, G wrote: > > > >> > I'm not receiving an oauth_verifier key/value pair in after the user > > >> > grants access through my app. > > > >> > I'm receiving the at the URL specified in my app settings and in my > > >> > initial token request. The callback I'm getting looks like this > > > >> >http://callback_url?oauth_token=xHddBl5uYQnSIESC4P16bmWS3ObDgMroXglEQ... > > > >> > Every issue I have seen regarding this has to do with not supplying > > >> > callback url's. I have included them in every step. I have even tried > > >> > to use it when asking for user authorization which the tutorial here: > > >> >http://dev.twitter.com/pages/authsaysIdon't need. I'm really at a > > >> > loss. > > > >> > I have tried to use the PIN method as well, but again the above > > >> > tutorial falls short at the critical step of what to do when the PIN > > >> > is aquired. > > > > -- > > > 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?hl=en -- 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?hl=en
[twitter-dev] Re: Missing oauth_verifier
Your questions helped me find the issue. I'm using oauth-php and apparently what I'm doing isn't properly setting the callback URL. I'll look for the oauth_callback_confirmed flag for my error checking. Thanks for the help! On Sep 6, 4:11 pm, Taylor Singletary wrote: > Can you share as much information about your request token step as > possible? This is the only step you should ever provide a callback URL > in. > > Can you verify that you are usinghttp://api.twitter.com/oauth/*for > all paths in this sequence. > What is the value of oauth_callback on your request token step? Is > this the only step that you are you providing this data? Are you > presenting this via a query string parameter, an authorization header, > a POST body, or any intermingling of the three? > > When you receive your response to request_token, do you get a > parameter that indicates oauth_callback_confirmed=true? > > Thanks, > Taylor > > > > On Mon, Sep 6, 2010 at 2:49 PM, G wrote: > > I will admit I'm not experienced with oauth at all and maybe I'm > > sending bad data in the initial step. I fail to see why I would get an > > appropriate request_token if that were the case though. > > > On Sep 6, 3:42 pm, Tom van der Woerdt wrote: > >> Strange, you aren't the first one who reported this. I really think that > >> this behavior should be investigated. > > >> Tom > > >> On 9/6/10 11:23 PM, G wrote: > > >> > I'm not receiving an oauth_verifier key/value pair in after the user > >> > grants access through my app. > > >> > I'm receiving the at the URL specified in my app settings and in my > >> > initial token request. The callback I'm getting looks like this > > >> >http://callback_url?oauth_token=xHddBl5uYQnSIESC4P16bmWS3ObDgMroXglEQ... > > >> > Every issue I have seen regarding this has to do with not supplying > >> > callback url's. I have included them in every step. I have even tried > >> > to use it when asking for user authorization which the tutorial here: > >> >http://dev.twitter.com/pages/authsaysI don't need. I'm really at a > >> > loss. > > >> > I have tried to use the PIN method as well, but again the above > >> > tutorial falls short at the critical step of what to do when the PIN > >> > is aquired. > > > -- > > 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?hl=en -- 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?hl=en
Re: [twitter-dev] Re: Missing oauth_verifier
Can you share as much information about your request token step as possible? This is the only step you should ever provide a callback URL in. Can you verify that you are using http://api.twitter.com/oauth/* for all paths in this sequence. What is the value of oauth_callback on your request token step? Is this the only step that you are you providing this data? Are you presenting this via a query string parameter, an authorization header, a POST body, or any intermingling of the three? When you receive your response to request_token, do you get a parameter that indicates oauth_callback_confirmed=true? Thanks, Taylor On Mon, Sep 6, 2010 at 2:49 PM, G wrote: > I will admit I'm not experienced with oauth at all and maybe I'm > sending bad data in the initial step. I fail to see why I would get an > appropriate request_token if that were the case though. > > On Sep 6, 3:42 pm, Tom van der Woerdt wrote: >> Strange, you aren't the first one who reported this. I really think that >> this behavior should be investigated. >> >> Tom >> >> On 9/6/10 11:23 PM, G wrote: >> >> >> >> > I'm not receiving an oauth_verifier key/value pair in after the user >> > grants access through my app. >> >> > I'm receiving the at the URL specified in my app settings and in my >> > initial token request. The callback I'm getting looks like this >> >> >http://callback_url?oauth_token=xHddBl5uYQnSIESC4P16bmWS3ObDgMroXglEQ... >> >> > Every issue I have seen regarding this has to do with not supplying >> > callback url's. I have included them in every step. I have even tried >> > to use it when asking for user authorization which the tutorial here: >> >http://dev.twitter.com/pages/authsays I don't need. I'm really at a >> > loss. >> >> > I have tried to use the PIN method as well, but again the above >> > tutorial falls short at the critical step of what to do when the PIN >> > is aquired. > > -- > 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?hl=en > -- 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?hl=en
[twitter-dev] Re: Missing oauth_verifier
I will admit I'm not experienced with oauth at all and maybe I'm sending bad data in the initial step. I fail to see why I would get an appropriate request_token if that were the case though. On Sep 6, 3:42 pm, Tom van der Woerdt wrote: > Strange, you aren't the first one who reported this. I really think that > this behavior should be investigated. > > Tom > > On 9/6/10 11:23 PM, G wrote: > > > > > I'm not receiving an oauth_verifier key/value pair in after the user > > grants access through my app. > > > I'm receiving the at the URL specified in my app settings and in my > > initial token request. The callback I'm getting looks like this > > >http://callback_url?oauth_token=xHddBl5uYQnSIESC4P16bmWS3ObDgMroXglEQ... > > > Every issue I have seen regarding this has to do with not supplying > > callback url's. I have included them in every step. I have even tried > > to use it when asking for user authorization which the tutorial here: > >http://dev.twitter.com/pages/authsays I don't need. I'm really at a > > loss. > > > I have tried to use the PIN method as well, but again the above > > tutorial falls short at the critical step of what to do when the PIN > > is aquired. -- 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?hl=en
[twitter-dev] Re: Missing oauth_verifier request parameter in OAuth CB
Hey guys, It seems with twitter4j, I had to specify a callback url. When I did this, I get a verifier. Not sure where the error lies. I'm using twitter4j-core-2.1.2. sb On Jun 23, 2:03 pm, sb wrote: > Hi Taylor, > > Thanks for getting back to me. I'm getting something like: > > http://example.com/oauthcb.htm?oauth_token=o7QdAbQYgpwAGKk2bR5j6VrARl... > > from Twitter. oauth_token is the same token sent initially during the > auth request per the spec. You bring up a good point about the > callback url and adding state. I'll address that once this issue is > resolved. > > I used to have this as a client application, and when doing that, I > would get a verification code in the browser that I could pass using > oauth_verifier. This worked fine. Does the app need to be registered > with @Anywhere? > > Thanks, > > sb > > On Jun 23, 10:46 am, Taylor Singletary > wrote: > > > > > Hi sb, > > > I'm surprised that you're not getting the oauth_verifier in the OAuth > > callback -- do you have an example of the complete callback URL you receive? > > > While it shouldn't matter, I do recommend always specifying your > > oauth_callback, regardless of having a default callback URL specified. It > > keeps intent clear in your code and most closely adheres to best practices > > while using OAuth. It also gives you an opportunity to pass some state on > > your callback URL without having to rely on a session. > > > Taylor > > > On Wed, Jun 23, 2010 at 7:36 AM, sb wrote: > > > Hello, > > > > I've recently registered an application with Twitter (normal app - not > > > @Anywhere) and I intend to use OAuth with it. I can see the > > > callback_url is being hit properly, but there is no oauth_verifier > > > request parameter. I only see oauth_token. > > > > I'm using twitter4j-core-2.1.x to do the heavy lifting of this, and > > > I'm not specifying a callback url when I request a token since I have > > > one in the application settings already. Do I need to specify the > > > callback URL anyway? > > > > Thanks, > > > > sb
[twitter-dev] Re: Missing oauth_verifier request parameter in OAuth CB
Hi Taylor, Thanks for getting back to me. I'm getting something like: http://example.com/oauthcb.htm?oauth_token=o7QdAbQYgpwAGKk2bR5j6VrARl... from Twitter. oauth_token is the same token sent initially during the auth request per the spec. You bring up a good point about the callback url and adding state. I'll address that once this issue is resolved. I used to have this as a client application, and when doing that, I would get a verification code in the browser that I could pass using oauth_verifier. This worked fine. Does the app need to be registered with @Anywhere? Thanks, sb On Jun 23, 10:46 am, Taylor Singletary wrote: > Hi sb, > > I'm surprised that you're not getting the oauth_verifier in the OAuth > callback -- do you have an example of the complete callback URL you receive? > > While it shouldn't matter, I do recommend always specifying your > oauth_callback, regardless of having a default callback URL specified. It > keeps intent clear in your code and most closely adheres to best practices > while using OAuth. It also gives you an opportunity to pass some state on > your callback URL without having to rely on a session. > > Taylor > > > > On Wed, Jun 23, 2010 at 7:36 AM, sb wrote: > > Hello, > > > I've recently registered an application with Twitter (normal app - not > > @Anywhere) and I intend to use OAuth with it. I can see the > > callback_url is being hit properly, but there is no oauth_verifier > > request parameter. I only see oauth_token. > > > I'm using twitter4j-core-2.1.x to do the heavy lifting of this, and > > I'm not specifying a callback url when I request a token since I have > > one in the application settings already. Do I need to specify the > > callback URL anyway? > > > Thanks, > > > sb
[twitter-dev] Re: Missing oauth_verifier request parameter in OAuth CB
I should also note that I used to have the application registered as a client and would get a verification code when it was like that. This app is also registered as a normal app and not as an @Anywhere but hopefully that doesn't make a difference.. sb On Jun 23, 1:44 pm, sb wrote: > Hi Taylor, > > Thanks for getting back to me. I'm getting something like: > > http://example.com/oauthcb.htm?oauth_token=o7QdAbQYgpwAGKk2bR5j6VrARl... > > from Twitter. oauth_token is the same token sent initially during the > auth request per the spec. You bring up a good point about the > callback url and adding state. I'll address that once this issue is > resolved. > > Neel > > On Jun 23, 10:46 am, Taylor Singletary > wrote: > > > > > Hi sb, > > > I'm surprised that you're not getting the oauth_verifier in the OAuth > > callback -- do you have an example of the complete callback URL you receive? > > > While it shouldn't matter, I do recommend always specifying your > > oauth_callback, regardless of having a default callback URL specified. It > > keeps intent clear in your code and most closely adheres to best practices > > while using OAuth. It also gives you an opportunity to pass some state on > > your callback URL without having to rely on a session. > > > Taylor > > > On Wed, Jun 23, 2010 at 7:36 AM, sb wrote: > > > Hello, > > > > I've recently registered an application with Twitter (normal app - not > > > @Anywhere) and I intend to use OAuth with it. I can see the > > > callback_url is being hit properly, but there is no oauth_verifier > > > request parameter. I only see oauth_token. > > > > I'm using twitter4j-core-2.1.x to do the heavy lifting of this, and > > > I'm not specifying a callback url when I request a token since I have > > > one in the application settings already. Do I need to specify the > > > callback URL anyway? > > > > Thanks, > > > > sb
[twitter-dev] Re: Missing oauth_verifier request parameter in OAuth CB
Hi Taylor, Thanks for getting back to me. I'm getting something like: http://example.com/oauthcb.htm?oauth_token=o7QdAbQYgpwAGKk2bR5j6VrARljVACgHsNhN0nN1c from Twitter. oauth_token is the same token sent initially during the auth request per the spec. You bring up a good point about the callback url and adding state. I'll address that once this issue is resolved. Neel On Jun 23, 10:46 am, Taylor Singletary wrote: > Hi sb, > > I'm surprised that you're not getting the oauth_verifier in the OAuth > callback -- do you have an example of the complete callback URL you receive? > > While it shouldn't matter, I do recommend always specifying your > oauth_callback, regardless of having a default callback URL specified. It > keeps intent clear in your code and most closely adheres to best practices > while using OAuth. It also gives you an opportunity to pass some state on > your callback URL without having to rely on a session. > > Taylor > > > > On Wed, Jun 23, 2010 at 7:36 AM, sb wrote: > > Hello, > > > I've recently registered an application with Twitter (normal app - not > > @Anywhere) and I intend to use OAuth with it. I can see the > > callback_url is being hit properly, but there is no oauth_verifier > > request parameter. I only see oauth_token. > > > I'm using twitter4j-core-2.1.x to do the heavy lifting of this, and > > I'm not specifying a callback url when I request a token since I have > > one in the application settings already. Do I need to specify the > > callback URL anyway? > > > Thanks, > > > sb
