#2373 audit requirements for local provider
Closed: Invalid None Opened 7 years ago by jhrozek.

Ticket was cloned from Red Hat Bugzilla (product Red Hat Enterprise Linux 7): Bug 1115188

Please note that this Bug is private and may not be accessible as it contains confidential Red Hat customer information.

Description of problem:

To comply with an audit requirement, the following steps must be audited when administering the local provider database. Every audit log must provide the information whether the audited request was

To be audited:

- creation of user / group -- audit of user / group parameters

- modification of user / group -- audit of modified user / group parameters

- deletion of user / group

- creation/modification of user password

Fields changed

blockedby: =>
blocking: =>
changelog: =>
coverity: =>
design: =>
design_review: => 0
feature_milestone: =>
fedora_test_page: =>
milestone: NEEDS_TRIAGE => SSSD 1.12.1
review: True => 0
selected: =>
testsupdated: => 0

I'll add you to CC list of one BZ where we are still discussing the format of the audit data. Please wait with writing code until the discussion is over, but feel free to look at how the shadow-utils do auditing in the meantime.

owner: somebody => mzidek

Not needed for the CC evaluation after all, moving out of 1.12.1

milestone: SSSD 1.12.1 => SSSD 1.13 beta

Fields changed

mark: => 0

We're going to need auditing when we support the local backend.

keywords: => localauth
milestone: SSSD 1.13 beta => SSSD 1.13 backlog

Mass-moving tickets not planned for the 1.13 release to 1.14

milestone: SSSD 1.13 backlog => SSSD 1.14 beta

The local provider work will be done in 1.15

milestone: SSSD 1.14 beta => SSSD 1.15 beta
sensitive: => 0

The local provider is not being developed anymore, we developed the files provider instead. I suggest we close this ticket.

component: SSSD => Local Provider
review: 0 => 1
selected: => Not need

I agree with jhrozek's comment. Closing this ticket.

resolution: => wontfix
status: new => closed

Metadata Update from @jhrozek:
- Issue assigned to mzidek
- Issue set to the milestone: SSSD Future releases (no date set yet)

4 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/3415

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.