[RADIATOR] ServerTACACSPLUS logging improvements
Hartmaier Alexander
alexander.hartmaier at t-systems.at
Fri May 27 08:04:59 CDT 2016
Hi,
I've finished forwarding all logs from all our Radiator instances to
Elasticsearch through syslog-ng (no need to install custom software on
the Radiator Servers) and RabbitMQ.
The log messages emitted by ServerTACACSPLUS sadly lack all the standard
Radius attributes like Handler:Identifier, User-Name, Client-Identifier etc.
Is there a way to improve this situation?
The log messages in question are:
- Could not get peer name on TacacsplusConnection socket: Transport
endpoint is not connected
- Authorization permitted for $USERNAME at $IPADDR, group $GROUPNAME,
args service=shell cmd*
But there are also non-ServerTACACSPLUS messages that don't include
those infos where it would be nice to know which Handler/AuthBy
trigggered them (those come from an AuthBy LDAP2, but which one?):
- Connecting to 1.2.3.4:636 1.2.3.5:636
- Connected to 1.2.3.4:636
- Attempting to bind to LDAP server 1.2.3.4:636
Thanks, Alex
*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*
T-Systems Austria GesmbH Rennweg 97-99, 1030 Wien
Handelsgericht Wien, FN 79340b
*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*
Notice: This e-mail contains information that is confidential and may be privileged.
If you are not the intended recipient, please notify the sender and then
delete this e-mail immediately.
*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*
More information about the radiator
mailing list