[
https://issues.apache.org/jira/browse/JCLOUDS-178?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zack Shoylev updated JCLOUDS-178:
---------------------------------
Comment: was deleted
(was: I am on vacation until the 27th. If you have SDK questions, contact
drg-d...@lists.rackspace.com
Thanks!
)
> 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)
