Maybe the correct way to do this is to retrive 2 access token, one for the server (and performe login with everyauth) and one for the client (to performe other stuff)...
On 14 Feb, 09:16, Tiziano Rossi <[email protected]> wrote: > Thanks Dick! > Yes this is a possible solution... But i don't realize how implement a > clean solution, for example: > > 1) User login with FB, everyauth store in session the ID of the user. > [ I have redis that store the session for (for example) 3 hour.] > 2) After a while the user log out from facebook [or de-authorize my > app], so the accessToken become invalid, but it still loggedin in my > app. > 3) Everyauth don't know this and the next graph api call become > invalid.... > > At this time i must create another accessToken or something else... > How can i do this? > Everybody know how to handle this scenario? > > Thanks. > Tiziano. > > On 13 Feb, 23:26, Dick Hardt <[email protected]> wrote: > > > > > > > > > If you do not want your Facebook access_token to expire, you need to > > include offline_access in the scope when requesting it. > > > -- Dick > > > On Feb 13, 2012, at 1:12 PM, Tiziano Rossi wrote: > > > > Hi to all! > > > > I use everyauth in my app for permit facebook authentication... > > > After that i want to use tha accessToken to performe some graph api > > > call... (maybe client side for performance reason). > > > What is the correct way to do this? > > > I got the accessToken returned from findOrCreateUser, but this can > > > become invalid for variuos reason... How everyauth handle the > > > exiration of facebook accessToken? > > > In case that i save the accessToken in database (in order to use it in > > > future session) i can't know when it become invalid... > > > > I think that is the same thing for other platform (twitter, github, > > > etc...) > > > > How do you handle this scenario? > > > > Thanks to all! > > > Tiziano. > > > > P.S. One possibility is to ask another accessToken from client-side bu > > > javascript (but i think that this is not a clean solution). > > > > -- > > > Job Board:http://jobs.nodejs.org/ > > > Posting > > > guidelines:https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines > > > You received this message because you are subscribed to the Google > > > Groups "nodejs" group. > > > To post to this group, send email to [email protected] > > > To unsubscribe from this group, send email to > > > [email protected] > > > For more options, visit this group at > > >http://groups.google.com/group/nodejs?hl=en?hl=en -- Job Board: http://jobs.nodejs.org/ Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines You received this message because you are subscribed to the Google Groups "nodejs" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en
