One other aspect to authorization that I would add is logging and
reporting - who did what and when. This could be achieved by wrappers
in the actions and pluggable modules to some cobbler/syslog facilities.
I can think of all the sarbox audits that clients go thru on the
patching side, don't see how this would be any different.
A logging module and hook (independent of any authN/authZ features) is
definitely doable too. By default we could just use Python standard
logging, and users could replace the logger module with something more
site-specific if they really wanted to.
Excellent suggestion.
I'll add these to the RFE list.
-regards
Subhendu
_______________________________________________
et-mgmt-tools mailing list
et-mgmt-tools@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/et-mgmt-tools
_______________________________________________
et-mgmt-tools mailing list
et-mgmt-tools@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/et-mgmt-tools
