ForumsSearch

Search results for "Posted by bresslerz"

Author	Message
bresslerz	Posted May 17, 2016 in: Is there a way to get a non-expiring token? Score: 0 bresslerz Posted: May 17, 2016 Score: 0 So does my app have to persist the auth token and refresh token and go through all of that mess even though I am the only user that will ever use it? Darn! :(
bresslerz	Posted May 15, 2016 in: Is there a way to get a non-expiring token? Score: 0 bresslerz Posted: May 15, 2016 Score: 0 I have built a custom PHP web page to display on a kiosk in my house to show my daily tasks. It will only be used by me using my account. Is there a way that I can pass my client ID, secret, and some sort of token in a single call to get tasks for my account? I've been experimenting with Oauth and I've gotten it to work, but having to store the access token for a set period of time and track that time before having to use the refresh token seems like a pain to code using the session or worse having to create a database. In using twitter in the past from an Arduino, I could pass my client secret and a token (created through twitter's authorized interface) and it will always work. No need for storing tokens that expire... Any thoughts?

Author

Message

Posted May 17, 2016 in: Is there a way to get a non-expiring token?

Score: 0

bresslerz
Posted: May 17, 2016
Score: 0

So does my app have to persist the auth token and refresh token and go through all of that mess even though I am the only user that will ever use it?

Darn! :(

bresslerz

Posted May 15, 2016 in: Is there a way to get a non-expiring token?

Score: 0

bresslerz
Posted: May 15, 2016
Score: 0

I have built a custom PHP web page to display on a kiosk in my house to show my daily tasks. It will only be used by me using my account. Is there a way that I can pass my client ID, secret, and some sort of token in a single call to get tasks for my account?

I've been experimenting with Oauth and I've gotten it to work, but having to store the access token for a set period of time and track that time before having to use the refresh token seems like a pain to code using the session or worse having to create a database.

In using twitter in the past from an Arduino, I could pass my client secret and a token (created through twitter's authorized interface) and it will always work. No need for storing tokens that expire...

Any thoughts?