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 <[email protected]> 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 <[email protected]> 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
