On Thu, 9 Jun 2011 11:34:43 +0700, surajit ray
<mr.surajit.ray at gmail.com> wrote:
> Hi Andreas,
> 
> On 9 June 2011 01:41, Nina Jeliazkova <jeliazkova.nina at gmail.com> wrote:
>> On 8 June 2011 13:38, surajit ray <mr.surajit.ray at gmail.com> wrote:
>>
>>> Hi Nina, Andreas,
>>>
>>> In the A&A workflow a token has a certain life time after which it
>>> becomes invalid. So if someone starts a task and provides a token for
>>> dataset access and upload - the access will work as it is done
>>> immediately and the token is valid, however the upload will fail as by
>>> that time the token would become invalid (as the task takes a long
>>> time). One way would be store the user credentials on the server
>>> (Maxtox) which I think is not the correct thing to do. The credentials
>>> should exists only in one secure place.
>>>
>>
>> One solution could be to try to renew the token, while it is still valid.
>>
> 
> Whats the mechanism to renew tokens ?

I am not aware of any such (OpenSSO-internal) mechanism (which does not
mean it doesn't exist, however).
I see no apparent solution to the problem you mentioned besides raising
token lifetime globally.

Regards
Andreas