Bug 1665683

Summary:	RGW: presigned URL for PUT with metadata fails with: SignatureDoesNotMatch
Product:	[Red Hat Storage] Red Hat Ceph Storage	Reporter:	Ashish Singh <assingh>
Component:	RGW	Assignee:	Matt Benjamin (redhat) <mbenjamin>
Status:	CLOSED ERRATA	QA Contact:	Tejas <tchandra>
Severity:	medium	Docs Contact:	Aron Gunn <agunn>
Priority:	low
Version:	3.2	CC:	agunn, anharris, cbodley, ceph-eng-bugs, ceph-qe-bugs, hyelloji, kbader, knortema, mbenjamin, sweil, tchandra, tserlin
Target Milestone:	rc	Keywords:	Reopened
Target Release:	4.1	Flags:	hyelloji: needinfo-
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:	ceph-14.2.8-3.el8, ceph-14.2.8-3.el7	Doc Type:	Bug Fix
Doc Text:	.Ceph Object Gateway properly applies AWS request signing Previously, the Ceph Object Gateway did not properly apply an AWS request for signing headers, and was generating the following error message: ---- SignatureDoesNotMatch ---- With this release, the Ceph Object Gateway code was fixed to properly sign headers. This results in the signing request to succeed when requested.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-05-19 17:30:39 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:
Bug Depends On:
Bug Blocks:	1816167

Description Ashish Singh 2019-01-12 16:21:28 UTC

* Description of problem:

Pre-signed URLs for PUT without metadata works fine, however the
Pre-signed URL for PUT with metadata gives SignatureDoesNotMatch

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

* How reproducible:
Always

* Steps to Reproduce:

* Actual results:
Pre-signed URL's doesn't works.

* Expected results:
Pre-signed URL's with metadata should work.

* Additional info:
NA

Comment 4 Giridhar Ramaraju 2019-08-05 13:08:39 UTC

Updating the QA Contact to a Hemant. Hemant will be rerouting them to the appropriate QE Associate. 

Regards,
Giri

Comment 5 Giridhar Ramaraju 2019-08-05 13:10:05 UTC

Updating the QA Contact to a Hemant. Hemant will be rerouting them to the appropriate QE Associate. 

Regards,
Giri

Comment 13 errata-xmlrpc 2020-05-19 17:30:39 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, 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/RHSA-2020:2231