RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1311056 - Add a Secrets as a Service component
Summary: Add a Secrets as a Service component
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: sssd
Version: 7.3
Hardware: Unspecified
OS: Unspecified
Target Milestone: rc
: ---
Assignee: SSSD Maintainers
QA Contact: Steeve Goveas
Aneta Šteflová Petrová
Depends On:
Blocks: 1435299
TreeView+ depends on / blocked
Reported: 2016-02-23 09:56 UTC by Jakub Hrozek
Modified: 2020-05-02 18:16 UTC (History)
8 users (show)

Fixed In Version: sssd-1.14.0-6.el7
Doc Type: Enhancement
Doc Text:
Support for secrets as a service This update adds a responder named `secrets` to the System Security Services Daemon (SSSD). This responder allows an application to communicate with SSSD over a UNIX socket using the Custodia API. This enables SSSD to store secrets in its local database or to forward them to a remote Custodia server.
Clone Of:
: 1435299 (view as bug list)
Last Closed: 2016-11-04 07:16:27 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Github SSSD sssd issues 3954 0 None closed Add a Secrets as a Service component 2020-07-17 15:02:26 UTC
Red Hat Product Errata RHEA-2016:2476 0 normal SHIPPED_LIVE sssd bug fix and enhancement update 2016-11-03 14:08:11 UTC

Description Jakub Hrozek 2016-02-23 09:56:35 UTC
This bug is created as a clone of upstream ticket:

This component securely stores secrets on behalf of applications, and allows to route and store secrets centrally if needed.

See: https://fedorahosted.org/sssd/wiki/DesignDocs/SecretsService

Comment 1 Jakub Hrozek 2016-06-29 20:55:59 UTC

Comment 4 Marc Muehlfeld 2016-07-20 06:46:15 UTC
Jakub, can you please review the DocText to make sure it's correct like this?

Comment 5 Jakub Hrozek 2016-07-20 07:24:57 UTC
Sounds good to me, thank you.

Comment 6 Amith 2016-09-22 09:30:23 UTC
Verified the BZ on SSSD Version: sssd-1.14.0-43.el7.x86_64

Finished initial round of testing for the tech preview. Got the following test cases reviewed by DEV:

Case-01: Enable and verify sssd-secrets service.
Case-02: Test sssd behaviour by adding secrets to services directive.
Case-03: Test sssd behaviour by adding a secrets section
Case-04: Verify stored secret for a local user.
Case-05: Test SSSD behavior by adding a duplicate secret name.
Case-06: Verify a user's access rights to stored secrets.

Comment 8 errata-xmlrpc 2016-11-04 07:16:27 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.


Note You need to log in before you can comment on or make changes to this bug.