You are viewing a plain text version of this content. The canonical link for it is here.

Posted to notifications@jclouds.apache.org by "Andrew Gaul (JIRA)" <ji...@apache.org> on 2013/08/06 20:49:49 UTC

[jira] [Reopened] (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:all-tabpanel ]

Andrew Gaul reopened JCLOUDS-178:
---------------------------------


I reverted this commit to address JCLOUDS-231.  We still need some variant of this fix.
                
> 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
>            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