#151 Use the ELAPI event logger for audit information
Closed: Invalid None Opened 14 years ago by sgallagh.

We should direct all of our audit messages through ELAPI sinks.


Fields changed

milestone: SSSD 0.6.0 => SSSD 1.0 RC

Definitely not going to happen in SSSD 1.0

milestone: SSSD 1.0 RC => SSSD Deferred

Fields changed

proposed: => 1.2

Fields changed

milestone: SSSD Deferred => SSSD 1.2

Fields changed

milestone: SSSD 1.2 => SSSD 1.3

Fields changed

milestone: SSSD 1.3 => SSSD Deferred

Fields changed

rhbz: => 0

Since ELAPI is deprecated, we should close this ticket.

blockedby: =>
blocking: =>
changelog: =>
coverity: =>
design: =>
design_review: => 0
feature_milestone: =>
fedora_test_page: =>
mark: => 0
patch: => 0
review: => 1
selected: =>
sensitive: => 0

ELAPI is not being developed anymore, closing.

resolution: => wontfix
status: new => closed

Metadata Update from @sgallagh:
- Issue assigned to jhrozek
- Issue set to the milestone: SSSD Patches welcome

7 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/1193

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