You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@jclouds.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2015/03/18 12:07:38 UTC

[jira] [Commented] (JCLOUDS-178) A 401 error should result in re-authenticating for a new token

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

ASF GitHub Bot commented on JCLOUDS-178:
----------------------------------------

Github user asfgit closed the pull request at:

    https://github.com/apache/incubator-brooklyn/pull/502


> A 401 error should result in re-authenticating for a new token
> --------------------------------------------------------------
>
>                 Key: JCLOUDS-178
>                 URL: https://issues.apache.org/jira/browse/JCLOUDS-178
>             Project: jclouds
>          Issue Type: Bug
>          Components: jclouds-compute
>    Affects Versions: 1.6.2, 1.7.0
>            Reporter: Zack Shoylev
>            Assignee: Zack Shoylev
>             Fix For: 1.6.3, 1.7.0
>
>
> When a keystone service responds with a 401, this means the keystone token has expired. Jclouds has to then re-authenticate. Unfortunately, an extra condition in the retry was preventing this from happening.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)