[
https://issues.apache.org/jira/browse/JCLOUDS-178?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14040027#comment-14040027
]
ASF subversion and git services commented on JCLOUDS-178:
---------------------------------------------------------
Commit c417ddef6760fcad27baba34e6e1dbe92d5708b9 in jclouds's branch
refs/heads/master from [~shrinand]
[ https://git-wip-us.apache.org/repos/asf?p=jclouds.git;h=c417dde ]
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)
