andyhuangdev opened a new pull request, #11794: URL: https://github.com/apache/ozone/pull/11794
## What changes were proposed in this pull request? Revoking an S3 secret currently rejects existing STS tokens only while the secret is absent. Recreating a secret for the same access id allows unexpired tokens to pass the revocation checks again. This change records an STS revocation cutoff when a secret is revoked, so earlier tokens remain revoked after the secret is recreated. The leader stamps the cutoff before Ratis replication, and the apply path updates the cache and persists it through the response batch. Existing later cutoffs are preserved, and log entries without an attached cutoff retain their previous behavior. ## What is the link to the Apache JIRA [HDDS-17409](https://issues.apache.org/jira/browse/HDDS-17409) ## How was this patch tested? - Added regression tests covering cutoff persistence, secret recreation, preservation of later cutoffs, legacy entries, and missing secrets. - Passed 88 related unit tests. - Added a secure three-OM HA integration test using real signed STS tokens and RPC requests. It verifies revocation after secret recreation, cutoff persistence on all replicas, leader failover, and OM restart. It fails before the fix and passes after it. - Passed checkstyle. RAT recognizes the new file’s license; the full RAT check reports unrelated existing files. -- 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] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
