You are viewing a plain text version of this content. The canonical link for it is here.

Posted to notifications@jclouds.apache.org by "Andrew Phillips (JIRA)" <ji...@apache.org> on 2013/11/13 14:07:28 UTC

[jira] [Resolved] (JCLOUDS-372) oauth token cache expiry time is 3600 minutes, when it should be 3600 seconds

     [ https://issues.apache.org/jira/browse/JCLOUDS-372?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Andrew Phillips resolved JCLOUDS-372.
-------------------------------------

    Resolution: Fixed

> oauth token cache expiry time is 3600 minutes, when it should be 3600 seconds
> -----------------------------------------------------------------------------
>
>                 Key: JCLOUDS-372
>                 URL: https://issues.apache.org/jira/browse/JCLOUDS-372
>             Project: jclouds
>          Issue Type: Bug
>          Components: jclouds-labs, jclouds-labs-google
>    Affects Versions: 1.6.2
>            Reporter: Alex Heneveld
>            Assignee: Andrew Phillips
>             Fix For: 1.7.0, 1.6.3
>
>         Attachments: JCLOUDS-372.patch
>
>
> oauth tokens from GCE typically expire after 3600 seconds. the oauth cache however keeps tokens for 3600 *minutes*, resulting in an "invalid credentials" error if a compute service is used against GCE more than 1h after it is created.



--
This message was sent by Atlassian JIRA
(v6.1#6144)