[
https://issues.apache.org/jira/browse/JCLOUDS-589?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14036664#comment-14036664
]
Diwaker Gupta commented on JCLOUDS-589:
---------------------------------------
Folks, the PR seems ready (https://github.com/jclouds/jclouds/pull/399). This
issue is blocking us in production settings and so we'd like to see it in a
release ASAP -- really want to avoid rolling out a private jclouds build with
this patch :-)
> Port fix for JCLOUDS-178 to non-keystone-v2.0 auth implementations
> ------------------------------------------------------------------
>
> Key: JCLOUDS-589
> URL: https://issues.apache.org/jira/browse/JCLOUDS-589
> Project: jclouds
> Issue Type: Bug
> Components: jclouds-blobstore
> Affects Versions: 1.7.3
> Reporter: Shri Javadekar
> Assignee: Shri Javadekar
> Fix For: 1.8.0, 1.7.4
>
>
> As part of fixing JCLOUDS-178 [1], jclouds added a mechanism for
> re-authenticating when it got back a "401 Unauthorized" response. However,
> this fix only went into the Keystone v2.0 implementation. The problem still
> exists in the Keystone v1.1 and non-keystone auth implementations.
> This bug should track the porting of that fix to the keystone v1.1 and
> non-keystone auth implementations.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
