Creating access tokens using the oauth_callback parameter with /oauth/request_token

Dec 17, 2013 at 4:49 PM
Hi Linvi,

I have been getting to grips with your API and had a good look through the source code over the last few days and have not noticed any way in which to authorise an application using the callback mechanism with Twitter.

I.e. not having to have the user to enter a PIN number after allowing your application access to your twitter account, but instead using a callback URL on your own website to handle the verification step instead.

Is there something obvious I have missed, and if not is this something that you will be adding in future releases of the project and thus currently working on?

I only ask because as a task to familiarise myself with the OAuth process and your project I have taken the opportunity to create my own custom WebTokenCreator class to do exactly this, however I could not get it to implement the ITokenCreator interface provided in the project source code due to the way in which I had to modify the methods so that I could follow the authentication process using a callback URL.

I did reuse much of the code you already provided with the existing TokenCreator class and on some routines made a few minor adjustments and would therefore be more than happy to share this with you/others if this is of any use to the overall project?

Your library has saved me a lot of time integrating the Twitter API into our website developments and I see it as only fair to contribute back in any way if possible.

Kind regards,

Tim
Dec 17, 2013 at 6:55 PM
Edited Dec 17, 2013 at 6:56 PM
Hi Tim,

I have not noticed any way in which to authorise an application using the callback mechanism with Twitter. Is there something obvious I have missed?

No you have not missed anything, there is currently no solution provided by Tweetinvi to generate credentials through a website redirect.

Is there something obvious I have missed, and if not is this something that you will be adding in future releases of the project and thus currently working on?

The reason for this feature to be missing is simply that I do not have enough time to implement all the feature of Tweetinvi but this is definitely one of the most critical feature I should implement.

The multiple authentication system should be the new feature of the version 0.9.0.1. The issue with this is that the 0.9.0.0 which is currently being developed requires a lot of time because we are completely re-designing Tweetinvi to provide a better solution for developers.

I only ask because as a task to familiarise myself with the OAuth process and your project I have taken the opportunity to create my own custom WebTokenCreator class to do exactly this, however I could not get it to implement the ITokenCreator interface provided in the project source code due to the way in which I had to modify the methods so that I could follow the authentication process using a callback URL.

Yes I think I will have to change how the ITokenCreator so that a user can login with either a redirect or using a pin.

I did reuse much of the code you already provided with the existing TokenCreator class and on some routines made a few minor adjustments and would therefore be more than happy to share this with you/others if this is of any use to the overall project? Your library has saved me a lot of time integrating the Twitter API into our website developments and I see it as only fair to contribute back in any way if possible.

I would be more than happy to see your code. As I said I have currently so much in my plate that I would love to have some refreshment ;)
Thank you very much for making this offer :)

I will contact you through your contact page tonight.

Sincerely,
Linvi