Closed intelligence closed 10 years ago
I'd have to know a bit more about what you're trying to accomplish, but you should be storing the access token probably on each user record in your database.
I'm going to close this since this seems to be an issue with the OAuth flow and storing your tokens in a database vs an actual issue with the client. Let's reopen if you still have issues.
So I've managed to get things up and running, finally. But now I'm wondering about persistence. What would be the ideal solution of storing the given access token for later use? I don't want the visitors to have to go through the entire flow with authorization upon every interaction.
I thought the idea was that if the user already has authorized and gotten a access token, it would redirect directly through the callback, skipping the tumblr authorization screen.
How is the flow supposed to work? Been googling like crazy.
connect.php
callback.php