not sure, but i would think it would be ok. i think the token should already be url safe, but once again - not sure.
-igor On Sat, Dec 4, 2010 at 12:38 PM, Peter Karich <peat...@yahoo.de> wrote: > Igor, > > there is token_secure. So storing it in clean text should be ok, right? > Or do I need to encrypt (or at leat base64ing) it? > > Regards, > Peter. > >> store the token in a cookie and attempt to auto-reologin user based on it? >> >> -igor >> >> On Sat, Dec 4, 2010 at 11:51 AM, Peter Karich<peat...@yahoo.de> wrote: >>> >>> Hi, >>> >>> do you know of any examples for wicket which uses twitter's oAuth? >>> In my app I can easily login and use the twitter api, >>> but I'm kind of stuck how to avoid that the user needs to login every >>> time >>> after the session expires. >>> >>> Any other hints, links or best practices? >>> >>> Kind regards, >>> Peter. >>> >>> -- >>> http://jetwick.com twitter search prototype >>> >>> >>> --------------------------------------------------------------------- >>> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org >>> For additional commands, e-mail: users-h...@wicket.apache.org >>> >>> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org >> For additional commands, e-mail: users-h...@wicket.apache.org >> >> > > > -- > http://jetwick.com twitter search prototype > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
