You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@jclouds.apache.org by "Alex Heneveld (JIRA)" <ji...@apache.org> on 2013/11/11 15:46:18 UTC
[jira] [Commented] (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:comment-tabpanel&focusedCommentId=13819003#comment-13819003 ]
Alex Heneveld commented on JCLOUDS-372:
---------------------------------------
fix provided in https://github.com/jclouds/jclouds-labs-google/pull/14
> 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-google
> Affects Versions: 1.6.2
> Reporter: Alex Heneveld
>
> 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)