Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I’m attempting to use the Twitter API with the DotNetOpenAuth library.
I have a working sample that posts tweets, but unfortunately, it forces the user to authorize the application each time it starts up.
According to the Twitter docs, I can avoid that by storing the access token. I have done this.
My question is, how can I get DotNetOpenAuth to get a new request token and use an existing access token without forcing the user to authorize the app again?
I found a solution – I’m not sure if it’s optimal or not, but it works.
I simply store the
accessandaccess_secrettokens and dump them back into the token manager when the application is started again.