Skip to main content

Knowing what's going on in your network is key, for both security and user management. Setting up syslogging enables feeding logs to Splunk or other SIEMs for more visiblity.

We'll be adding rsyslog to the WiKID server itself.  This is for Centos/Redhat or our ISO/virtual image.  Let us know if you need Ubuntu instructions.  You can change the remote host as shown below if you prefer.

Install rsyslog:

# yum install rsyslog 

You need to disable syslog:

service syslog stop

Add the following to /etc/rsyslog.conf at the bottom of the file:

#load the kernel logger module
$ModLoad imklog
#load the UNIX sockets module to receive local messages from processen
$ModLoad imuxsock
#load UDP powers, to receive messages via the UDP protocol
$ModLoad imudp
#make rsyslog listen on all ip addresses, you could specify an address
#make rsyslog listen on UDP port 514
$UDPServerRun 514
#repeated lines will be reduced
$RepeatedMsgReduction on ()

Start rsyslog:

service rsyslog start

That's it for rsyslog, now let's tell WiKID to send the logs to syslog.

Edit the file /etc/WiKID/  Read the comments for instructions (as they may be more up-to-date than this doc).  In general, command the third line and uncomment the 5th line.  Then uncomment the lines for syslog.  The file should look like:

# Logging detail level,
# Must be one of ("trace", "debug", "info", "warn", "error", or "fatal").
#log4j.rootLogger=DEBUG, socketLogger

# comment the line above and uncomment the line below to use syslog
log4j.rootLogger=DEBUG, socketLogger, Syslog   

# comment out the rootLogger above and uncomment the line below to output logs to the console
#log4j.rootLogger=DEBUG, socketLogger,  A1

# Uncomment the lines below if using syslog
log4j.appender.Syslog.layout.ConversionPattern=%-5p %c{2} [%t,%M:%L] %m%n

# A1 is set to be a ConsoleAppender.

# A1 uses PatternLayout.
log4j.appender.A1.layout.ConversionPattern=%-4r [%t] %-5p %c %x - %m%n

NB:  You can change the line 'log4j.appender.Syslog.SyslogHost=localhost' to point to a remote host if you prefer.

Now, run:

tail -f /var/log/messages

And login to a see the logs.  Here's a typical log where a user gets an OTP from the WiKID software token, the server validates it and grants access:

Sep 12 10:20:35 localhost.localdomain user: INFO  server.DeviceTransactionExec [http-bio-80-exec-3,processPasscodeRequest:717] Issued passcode to device -2607729168221619508
Sep 12 10:20:39 localhost.localdomain user: INFO  access.WikidAccess4 [Session.0,authenticate:293] Access granted for nowen, domain code: 192168001102 client: /
Sep 12 10:20:39 localhost.localdomain user: INFO  log.DBSvrLogImpl [Session.0,write:44] <7> Access-Accept(2) LEN=115 Access-Request by nowen succeeded


Copyright © WiKID Systems, Inc. 2019 | Two-factor Authentication