jclouds-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrew Gaul (JIRA)" <j...@apache.org>
Subject [jira] [Reopened] (JCLOUDS-178) A 401 error should result in re-authenticating for a new token
Date Tue, 06 Aug 2013 18:49:49 GMT

     [ 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

Mime
View raw message