[
https://issues.apache.org/jira/browse/HADOOP-19648?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18016067#comment-18016067
]
ASF GitHub Bot commented on HADOOP-19648:
-----------------------------------------
cnauroth commented on PR #7867:
URL: https://github.com/apache/hadoop/pull/7867#issuecomment-3221459343
@leosanqing , thank you for the reminder. I have committed this to trunk.
This would ship the fix in Hadoop 3.5.0. I looked at backporting to branch-3.4,
but there were conflicts. If you need the patch in earlier versions, please
send up a separate pull request targeting branch-3.4. Thank you for the
contribution!
> cos use token credential will lost token field
> ----------------------------------------------
>
> Key: HADOOP-19648
> URL: https://issues.apache.org/jira/browse/HADOOP-19648
> Project: Hadoop Common
> Issue Type: Bug
> Components: cloud-storage, fs/cos
> Affects Versions: 3.3.0
> Reporter: sanqingleo
> Priority: Critical
> Labels: pull-request-available
> Attachments: image-2025-08-11-10-37-12-451.png,
> image-2025-08-11-10-42-36-375.png
>
>
> Hi,
> I've discovered a bug when accessing COSN using temporary credentials (access
> key, secret key, and session token).
> In the org.apache.hadoop.fs.cosn.CosNativeFileSystemStore#initCOSClient
> method, when the client is initialized, it only passes the access key and
> secret key, completely ignoring the session token. This causes all subsequent
> operations that rely on these temporary credentials to fail.
> Furthermore, this re-initialization step seems unnecessary. Instead of
> creating a new client with incomplete credentials, the existing credential
> provider (which already contains the AK, SK, and token) should be passed down
> directly.
> !image-2025-08-11-10-37-12-451.png|width=1048,height=540!
> !image-2025-08-11-10-42-36-375.png!
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]