I guess my question was more... What do I need to do as a container implementer and a gadget writer to ensure I am getting my tokens refreshed? Is this suppose to be automatic or is there some work I have to do?
doug On 2/13/13 5:22 PM, "Dan Dumont" <ddum...@gmail.com> wrote: > Shindig should be able to take valid container tokens and mint new gadget > tokens as-is. > Container tokens will need to be minted by you somehow. You'll want to use > the same crypter/codec and key that shindig will use to decode them. > > On Wed, Feb 13, 2013 at 9:20 AM, Doug Davies <davi...@oclc.org> wrote: > >> > I was reading this wiki page >> > >> > https://cwiki.apache.org/SHINDIG/security-tokens.html >> > >> > I know there has been some work on gadget refresh tokens in the 2.5 beta >> > releases. Can someone briefly tell me that state of refreshing both >> > container and gadget tokens in 2.5? Do either require that my >> > authentication server support the refresh token call? What am I required >> > to >> > implement and what should happen automatically? >> > >> > Thanks, >> > doug >> > >
