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

Posted to common-issues@hadoop.apache.org by "Vinod Kumar Vavilapalli (JIRA)" <ji...@apache.org> on 2015/10/26 19:29:28 UTC

[jira] [Updated] (HADOOP-12208) Wrong token in the authentication header when there is re-authentication request

     [ https://issues.apache.org/jira/browse/HADOOP-12208?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Vinod Kumar Vavilapalli updated HADOOP-12208:
---------------------------------------------
    Target Version/s: 2.7.2
       Fix Version/s:     (was: 2.7.2)

[~gvernik], FYI, you should use target-version for your intention. Fix-version is set at commit time. I'm fixing this for now.

> Wrong token in the authentication header when there is re-authentication request
> --------------------------------------------------------------------------------
>
>                 Key: HADOOP-12208
>                 URL: https://issues.apache.org/jira/browse/HADOOP-12208
>             Project: Hadoop Common
>          Issue Type: Bug
>          Components: fs/swift
>    Affects Versions: 2.6.0
>            Reporter: Gil Vernik
>            Assignee: Gil Vernik
>         Attachments: token-header-fix-0001.patch
>
>
> When authentication token expires, Swift returns 401. In this case the exec method from SwiftRestClient catches this exception and performs another authentication request to renew the token. If authentication successful, exec method retry original request. However, the bug is that retry still uses old token in a header and doesn't update it with a new one.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)