Bugzilla – Bug 3145
Removal of persisted delegatd credentials that have expired
Last modified: 2008-04-24 09:04:49
You need to
before you can comment on or make changes to this bug.
Currently the infrastructure provided by Java core is used to clean up the
expired delegated credentials. But this works only for credentials in memory.
Need to add a scheme that periodically cleans up expired credentials persisted
to disk. (A thread that is run sporadically and maybe also takes the file
timestamp into consideration to see when resource was last accessed)
This probably could be made more generic and added to core.
If this is going to be made general then I would request that we make it
reasonably easy to plug in other
actions as well (or at least make the sweeper easily overridable). One of the
things that still needs to be
done in my recent subscription commit is to add functionality to a sweeper that
removes empty directories
after the notification producer resource on which the subscription was acting
Reassigning to current wsrf developer to close/fix as appropriate
To clarify this issue: as long as the container is running, the resource
sweeper thread deletes expired resources and deletes the persisted file also.
But if the container is shut down and if the resource expires when the
container is down, the expired resources are not automatically deleted. If an
attempt is made to access the expired resource, once the container starts up,
the persisted file is cleaned up and a ResourceUnknownFault is thrown.