Bug 1708798 - rgw: luminous: keystone: backport keystone S3 credential caching
Summary: rgw: luminous: keystone: backport keystone S3 credential caching
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Ceph Storage
Classification: Red Hat Storage
Component: RGW
Version: 3.2
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: rc
: 3.3
Assignee: Matt Benjamin (redhat)
QA Contact: Tejas
URL:
Whiteboard:
Depends On:
Blocks: 1726135 1952466
TreeView+ depends on / blocked
 
Reported: 2019-05-10 21:34 UTC by Matt Benjamin (redhat)
Modified: 2021-04-22 10:31 UTC (History)
11 users (show)

Fixed In Version: RHEL: ceph-12.2.12-8.el7cp Ubuntu: ceph_12.2.12-6redhat1
Doc Type: Enhancement
Doc Text:
.Keystone S3 credential caching has been implemented The Keystone S3 credential caching feature permits using AWSv4 request signing (`AWS_HMAC_SHA256`) with Keystone as an authentication source, and accelerates Keystone authentication using S3. This also enables AWSv4 request signing, which increases client security.
Clone Of:
: 1952466 (view as bug list)
Environment:
Last Closed: 2019-08-21 15:10:58 UTC
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github ceph ceph pull 26095 0 None closed rgw: Added caching for S3 credentials retrieved from keystone 2021-04-19 13:49:44 UTC
Red Hat Product Errata RHSA-2019:2538 0 None None None 2019-08-21 15:11:09 UTC

Description Matt Benjamin (redhat) 2019-05-10 21:34:21 UTC 
Backport mechanism which permits validation of awsv4 signatures and accelerates same, without requirement to use temporary credentials.
Comment 8 errata-xmlrpc 2019-08-21 15:10:58 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-2019:2538
Note You need to log in before you can comment on or make changes to this bug.