A notification system for changes or warnings would be very useful. It should be general enough, so that it can be hooked to different outputs - mail, message queues (AMQP) or even SNMP traps. It can be a lightweight incarnation of a general message system like fedmsg.
Use Cases
Sources of information The original use case for this information were notifications triggered by framework (e.g. adding new user). However, there are other sources where people may like to get notifications from, based on complexity and granularity of this system
Base architecture Given that multiple sources may be useful, the most universal system for transmitting and collecting notifications would be D-BUS. There should be a central daemon, possibly oddjob-based, that would relay it to a message queuing software for further delivery.
Calling DBUS from Python code is straightforward, certmonger and SSSD already have DBUS interface that could be extended. Other components (389-DS or Kerberos KDC) would need to be extended first.
See https://fedorahosted.org/freeipa/ticket/3095 for another use case.
There is an existing thesis topic proposal for this RFE: https://thesis-managementsystem.rhcloud.com/topic/show/312/general-notification-system-for-freeipa
The student had given up the project for personal reasons so it is free for anyone to take.
Here are [of source code]] and [https://github.com/pkubatrh/dip/blob/master/doc/obsah.tex|text] which the student wrote before he left. These are GPLv3 licensed and can be used for inspiration.
Do not hesistate to contact [https://www.redhat.com/mailman/listinfo/freeipa-devel|freeipa-devel] mailing list if you are interested in this!
Metadata Update from @ssieb: - Issue set to the milestone: Ticket Backlog
Login to comment on this ticket.