Hi, Yes, pin should be passed to the API as a post param. The *get* part of the method name *get*OAuthAccessToken() doesn't indicate that it uses GET method internally. It actually uses POST method to retrieve access tokens.
see also: http://yusuke.homeip.net/twitter4j/en/javadoc/twitter4j/Twitter.html#getOAuthAccessToken(java.lang.String,%20java.lang.String,%20java.lang.String) Cheers, Yusuke On 7月4日, 午後3:08, alien9 <alienjazz...@gmail.com> wrote: > I'm not sure what to do with the PIN. I didn't see a clear place to > add it (figured in the RequestToken, before calling for AccessToken). > > I grabbed the SNAPSHOT source, as well, and followed code through to > HttpClient.getOAuthAccessToken.. I"m guessing the pin should get added > there as a POST param? > > On Jun 10, 10:10 am, Yusuke Yamamoto <yus...@mac.com> wrote: > > > > > Hi all, > > > A snapshot build of Twitter4J 2.0.8 is > > available.http://yusuke.homeip.net/hudson/job/Twitter4J/212/net.homeip.yusuke$t...... > > > This version supports PIN-based authentication shipped with > > OAuth1.0a.http://groups.google.com/group/twitter-api-announce/browse_frm/thread... > > > There's no impact with OAuth1.0a on existing browser clients. > > But desktop clients using Twitter4J with OAuth authentication need to > > migrate to this version immediately in order to allow users to input > > pin upon Access Token retrieval. > > > This is a snapshot build, however existing automated test cases passed > > successfully and it should be stable enough to put in production > > environments. > > > Twitter4J 2.0.8 will be generally available in the maven central > > repository in a few days with small bug fixes. > > > Thanks, > > -- > > Yusuke Yamamoto > > yus...@mac.com > > > this email is: [x] bloggable/twittable [ ] ask first [ ] private > > follow me on :http://twitter.com/yusukeyamamoto > > subscribe me :http://yusuke.homeip.net/blog/