#2913 Add a Secrets as a Service component
Closed: Fixed None Opened 5 years ago by simo.

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


Assigning to simo for now and moving to 1.14. There might be subtasks assigned either to me or Christian, details tbd

milestone: NEEDS_TRIAGE => SSSD 1.14 alpha

Fields changed

rhbz: => todo

Fields changed

blockedby: => #1552

Fields changed

priority: major => critical

Fields changed

owner: somebody => simo

Fields changed

patch: 0 => 1

The patches are on review, but I would like to release 1.14 alpha today, therefore moving to 1.14 beta.

milestone: SSSD 1.14 alpha => SSSD 1.14 beta

Metadata Update from @simo:
- Issue assigned to simo
- Issue marked as depending on: #1552
- Issue set to the milestone: SSSD 1.14 beta

3 years ago

SSSD is moving from Pagure to Github. This means that new issues and pull requests
will be accepted only in SSSD's github repository.

This issue has been cloned to Github and is available here:
- https://github.com/SSSD/sssd/issues/3954

If you want to receive further updates on the issue, please navigate to the github issue
and click on subscribe button.

Thank you for understanding. We apologize for all inconvenience.

Login to comment on this ticket.

Metadata