Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
This project is now read‑only. Starting Monday, February 2, please use https://ibm-ceph.atlassian.net/ for all bug tracking management.

Bug 2260133

Summary: [IBM Support] MinIO client getting 403 when trying to access objects after upgrade to 5.3
Product: [Red Hat Storage] Red Hat Ceph Storage Reporter: Sergii Mykhailushko <smykhail>
Component: RGWAssignee: Pritha Srivastava <prsrivas>
Status: CLOSED ERRATA QA Contact: Hemanth Sai <hmaheswa>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 5.3CC: ceph-eng-bugs, cephqe-warriors, hmaheswa, mbenjamin, mkasturi, prsrivas, rpollack, tserlin
Target Milestone: ---   
Target Release: 8.0   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: ceph-19.1.1-49.el9cp Doc Type: No Doc Update
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2024-11-25 09:00:29 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Sergii Mykhailushko 2024-01-24 16:02:48 UTC 
Description of problem:

We have a customer who are hitting issues with STS+RGW combination. The culprit here is that according to them the problem appeared after 4.3 → 5.3 upgrade. They're leveraging MinIO STS API with Keycloak identity provider (AssumeRoleWithWebIdentity), and when users try to access objects with that, they get 403 errors form S3. When using the same configuration, security policies and STS credentials in boto3 script, it all works fine. So it's only MinIO client that fails. In debug rgw logs we're getting almost nothing when there is incoming request from minio, apart of the failed auth itself:

~~~
debug 2024-01-22T14:43:21.118+0000 7f5f6e4a2700 20 req 9527874993133805353 0.000000000s s3:get_obj rgw::auth::s3::AWSAuthStrategy: trying rgw::auth::s3::STSAuthStrategy   
...
debug 2024-01-22T14:43:21.118+0000 7f5f6e4a2700  5 req 9527874993133805353 0.000000000s s3:get_obj Failed the auth strategy, reason=-1                                     
debug 2024-01-22T14:43:21.118+0000 7f5f6e4a2700 10 failed to authorize request                                                                                             
debug 2024-01-22T14:43:21.118+0000 7f5f6e4a2700  1 req 9527874993133805353 0.000000000s op->ERRORHANDLER: err_no=-1 new_err_no=-1  
~~~

Version-Release number of selected component (if applicable):

IBM Storage Ceph 5.3
Comment 24 errata-xmlrpc 2024-11-25 09:00:29 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (Red Hat Ceph Storage 8.0 security, bug fix, and enhancement updates), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2024:10216