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 subversion and git services (JIRA)" <ji...@apache.org> on 2014/06/22 05:34:24 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=14040025#comment-14040025 ] 

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

Commit 3d4d5aded8bda2d4aee3d317a957529e4b74fb6d in jclouds's branch refs/heads/1.7.x from [~shrinand]
[ https://git-wip-us.apache.org/repos/asf?p=jclouds.git;h=3d4d5ad ]

JCLOUDS-589: Reauthenticate on Keystone HTTP 401

This commit ports the Keystone 2.0 fix from JCLOUDS-178 to Keystone
1.1.


> 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.7.0, 1.6.2
>            Reporter: Zack Shoylev
>            Assignee: Zack Shoylev
>             Fix For: 1.7.0, 1.6.3
>
>
> 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.2#6252)