Bug 1777064 - [RFE] rgw: support Hashcorp Vault as secrets store for S3 SSE-KMS
Summary: [RFE] rgw: support Hashcorp Vault as secrets store for S3 SSE-KMS
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Ceph Storage
Classification: Red Hat Storage
Component: RGW
Version: 4.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: rc
: 4.1
Assignee: Matt Benjamin (redhat)
QA Contact: Tejas
URL:
Whiteboard:
Depends On:
Blocks: 1812060
TreeView+ depends on / blocked
 
Reported: 2019-11-26 21:02 UTC by Matt Benjamin (redhat)
Modified: 2020-05-19 17:31 UTC (History)
9 users (show)

Fixed In Version: ceph-14.2.8-30.el8cp, ceph-14.2.8-23.el7cp
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1812060 (view as bug list)
Environment:
Last Closed: 2020-05-19 17:31:24 UTC
Embargoed:
hyelloji: needinfo-

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Ceph Project Bug Tracker 41062 0 None None None 2019-11-26 21:02:43 UTC
Github ceph ceph pull 29783 0 None closed rgw: add SSE-KMS with Vault using token auth 2021-01-26 16:41:23 UTC
Github ceph ceph pull 31025 0 None closed rgw: improvements to SSE-KMS with Vault 2021-01-26 16:40:40 UTC
Github ceph ceph pull 31361 0 None closed rgw: extend SSE-KMS with Vault using transit secrets engine 2021-01-26 16:40:40 UTC
Red Hat Product Errata RHSA-2020:2231 0 None None None 2020-05-19 17:31:57 UTC

Description Matt Benjamin (redhat) 2019-11-26 21:02:43 UTC 
Description of problem:
Adds an integration mechanism for storing SSE-KMS (S3 server-managed encryption) secrets in Hashcorp Vault key-management infrastructure.
Comment 13 errata-xmlrpc 2020-05-19 17:31:24 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
Note You need to log in before you can comment on or make changes to this bug.