Help desk support of authn/authz failures? Logging detailed messages to SQL?

[Alan Buxey]

hi,

firstly, deployment tool - such as CloudPath xpressconnect or sux1 to ensure
that the user is doing the least amount possible to mess things up (also ensures
that all the right things such as validate server, RADIUS name etc are all properly
defined).

secondly, capture the output of the logfile (Perl Tail File module is nice) - which
is why I wanted the radiusd.log file to be the right one - logrotate really messes
the recent 2.1.x logfile up - so i now have a manual restart of the server along
with log rotation.....hmm..  and putting data (detail file stuff too) into  a database with
a nice web front end for 'low level access' is a must.

there have been discussions in europe about way of logging the reason for a failure and
putting it onto a sites secure web area so that users can log in and see why things arent
working for them....

alan