Bug 238558 - Token manager returns expired token
Summary: Token manager returns expired token
Status: NEW
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: Geclipse (show other bugs)
Version: unspecified   Edit
Hardware: All All
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Ariel Garcia CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-06-26 07:39 EDT by Pawel Wolniewicz CLA
Modified: 2014-01-09 16:01 EST (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Pawel Wolniewicz CLA 2008-06-26 07:39:34 EDT 
When the token created and activated expire it is still returned by Token Manager without reactivation. 
Probably isValid method should be corrected because definitely token is not valid in the user sense.
Comment 1 Pawel Wolniewicz CLA 2008-06-26 07:55:16 EDT 
Two additional thoughts:

1. It would be nice to have a way to request the token which is valid for at least given number of seconds (hours?). If submission plugin know that the given type of job reauires at least X hours it could request such token to ensure that it will not expire during job execution.

2. There should be the way of distinguishing reactivated token from the previous one. Recommended solution is that token.getID() returns unique ID (reqctivated token will have other ID). My usecase: to submit job to WMS or CREAM first proxy must be delegated. When I request token from the token manager I check if that token (by ID) was already delegated. When I will get reactivated token it still have the same ID, so proxy is not delegated.