FYI. I've redeployed on the test cluster. This required updating jars too. --Shane On Feb 5, 2014, at 10:42 AM, Gavin Price <[email protected]> wrote:

Re the short term plan, the Java auth libs and workspace service have been updated and I've requested a redeploy.

-g

On 2/4/2014 6:49 PM, Gavin A Price wrote:

...

I'm moving this conversation from the 'hosed again' thread since otherwise people might miss it based on the title.

In brief: currently the Java auth libs enforce a 3 day lifetime on tokens. The issue is with long running jobs - if a user's token is close to expiry when a job starts, or if the job is days long, the job will not be able to save data to any service that uses the Java auth libs, including the workspace service. From a security perspective, however, 3 days seems like a fairly long time for tokens to live if they start leaking.

The proposal is:

Short term: Increase the lifetime to 60 days in the Java auth libs.

Long term: Decide on and implement a kbase wide token lifetime. Support necessary functionality for long running jobs given that lifetime.

I'll change the Java libs and request a workspace redeploy tomorrow unless I hear differently.

-g _______________________________________________ Kbase-devel mailing list [email protected] https://lists.kbase.us/mailman/listinfo/kbase-devel

_______________________________________________ Kbase-devel mailing list [email protected] https://lists.kbase.us/mailman/listinfo/kbase-devel