zhangshenghang commented on PR #12730:
URL: https://github.com/apache/seatunnel/pull/12730#issuecomment-6731043708

   Agreed — the tokenless STS workaround was misleading. Fixed in 7c018b613 
(both languages): the OBS STS section now states that this connector cannot 
currently use OBS STS temporary credentials, because 
`ObsConf.buildWithReadonlyConfig` installs only `access_key`, `access_secret`, 
and `endpoint` and there is no pass-through for the session token that OBS STS 
credentials always carry, so token-bound temporary credentials fail at 
connection time. It also notes that carrying a security token or a credential 
provider would require a separate, tested connector change, and recommends a 
long-lived AK/SK with a least-privilege policy scoped to the target bucket 
prefix instead. The STS example block was removed with it.
   
   An empty "Trigger CI" commit (f6b48a426) was pushed on top so the fork's 
Build workflow runs on the new head.
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to