[
https://issues.apache.org/jira/browse/HADOOP-19648?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18014835#comment-18014835
]
ASF GitHub Bot commented on HADOOP-19648:
-----------------------------------------
leosanqing commented on PR #7867:
URL: https://github.com/apache/hadoop/pull/7867#issuecomment-3199934458
> @leosanqing , thank you for the patch. I commented with a few suggestions.
>
> Can you or someone else make sure the integration tests are passing? I
don't have the means to run those myself.
Thx bro.
Sure, I'v added a new ITest, and pass the test on my local env.(the failed
tests are Junit method not found, I've looked up each failed tests)
<img width="2510" height="481" alt="image"
src="https://github.com/user-attachments/assets/f3f6b152-6dc5-471f-8dbb-f21e4d55c33c"
/>
When I'm not change code. This ITest will throw exception like this.
<img width="2419" height="1374" alt="image"
src="https://github.com/user-attachments/assets/f381bc6d-0ab7-4a1e-920d-0fae8e6eb3e5"
/>
and this is the new code for testing.
<img width="2509" height="475" alt="image"
src="https://github.com/user-attachments/assets/69ad045e-449b-47ca-b13c-6d606767c099"
/>
> 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
> 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]