Mailing-List: contact dev-help@shindig.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@shindig.apache.org
Received-SPF: pass (athena.apache.org: domain of ddumont@gmail.com designates
 209.85.217.180 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <CD410B6D.9EC8%daviesd@oclc.org>
References: <CD410B6D.9EC8%daviesd@oclc.org>
Date: Wed, 13 Feb 2013 17:22:41 -0500
Message-ID: 
 <CAG+p7DsXOxLy6KK-VrfaFU=2RP0i_1xs8rLCpW2KcOfWpp5z-Q@mail.gmail.com>
Subject: Re: State of security tokens
From: Dan Dumont <ddumont@gmail.com>
To: dev@shindig.apache.org
Content-Type: multipart/alternative; boundary=bcaec55241069bc4d204d5a2947e

--bcaec55241069bc4d204d5a2947e
Content-Type: text/plain; charset=UTF-8

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 <daviesd@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
>

--bcaec55241069bc4d204d5a2947e--