[
https://issues.apache.org/jira/browse/JCLOUDS-178?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13732064#comment-13732064
]
Zack Shoylev commented on JCLOUDS-178:
--------------------------------------
It seems to me this can happen for any authenticated request, so yes.
> 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
>
> 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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
