You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ozone.apache.org by "Fabian Morgan (Jira)" <ji...@apache.org> on 2026/03/31 00:49:00 UTC

[jira] [Created] (HDDS-14935) [STS] Handle Latent Inconsistencies in S3 API Acl Checks

Fabian Morgan created HDDS-14935:
------------------------------------

             Summary: [STS] Handle Latent Inconsistencies in S3 API Acl Checks
                 Key: HDDS-14935
                 URL: https://issues.apache.org/jira/browse/HDDS-14935
             Project: Apache Ozone
          Issue Type: Sub-task
            Reporter: Fabian Morgan
            Assignee: Fabian Morgan


Currently, S3 APIs are not consistent in how ACL checks are applied.  For example, `PutObject` (i.e. OMKeyCreateRequest, OMAllocateBlockRequest, OMKeyCommitRequest), `DeleteObject` (i.e. OMKeyDeleteRequest), `PutObjectTagging` (i.e. S3PutObjectTaggingRequest), etc. perform their ACL checks in `preExecute()` which is on the OM leader RPC thread.  

However, APIs like `DeleteBucket` (i.e. OMBucketDeleteRequest), `PutBucketAcl` (i.e. OMBucketAclRequest), etc. perform their ACL checks in `validateAndUpdateCache()` which is on the Ratis apply thread.  This affects STS in that the STSTokenIdentifier ThreadLocal currently is not available on the Ratis apply thread, so if the STS token has an inline session policy, some ACL checks that should pass would fail.  This ticket addresses the inconsistency by ensuring the ThreadLocal is always available on the Ratis apply thread via updates to OzoneManagerStateMachine.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@ozone.apache.org
For additional commands, e-mail: issues-help@ozone.apache.org