2 replies to this topic

[TomatoBin]

After successfully implementing oAuth in my application (based off the PHP SDK sample) I can go ahead and use the API properly to add/update notes in a users account.

However, if I come back to my application the next day...I no longer have access and the user must go through the oauth process and re-authorize the application again.

Can I store some of the oauth values in my database, and use them to authenticate a user at anytime?

If so, what values do I need to store? ...there's the oAuth verifier, access token identifier, access token secret.
Do I need to store all three of those values and is storing them in my database an ok method?

Thanks in advance for any help

[Julien Boedec]

Yes, you may store the authentication token and the noteStore URL in a database. That information is enough to avoid re authenticating.

[TomatoBin]

Thanks Julien for the reply!!

This sounds like exactly what I need. So I dont need the token secret? Would I ever need that?

Also when you say noteStore URL, I don't see a URL per se...I do see a "Shard id" but thats it. Do I have to create the url myself?

Thanks