jclouds-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (JCLOUDS-372) oauth token cache expiry time is 3600 minutes, when it should be 3600 seconds
Date Tue, 12 Nov 2013 11:11:17 GMT

    [ https://issues.apache.org/jira/browse/JCLOUDS-372?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13820015#comment-13820015
] 

ASF subversion and git services commented on JCLOUDS-372:
---------------------------------------------------------

Commit 4e6892116819c320d7dd99d0708304b3e670ccd3 in branch refs/heads/master from [~alex.heneveld]
[ https://git-wip-us.apache.org/repos/asf?p=jclouds-labs-google.git;h=4e68921 ]

JCLOUDS-372: changing OAuth timeout from MINUTES to SECONDS


> 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
>            Assignee: Andrew Phillips
>             Fix For: 1.7.0
>
>         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)

Mime
View raw message