If a Syslog-ng Windows Event Collector (WEC) server is installed on a system that also has Safeguard Authentication Services (SAS) installed on it then the SAS host.keytab can be used for Kerberos authentication or else a new keytab can be can created by SAS and used instead.
These keytabs can be used instead of the independent method detailed in the “Syslog-ng PE Windows Event Collector Administration Guide”
In the following examples ‘wecsrv.domain.com’ is used as the FQDN of the Syslog-ng WEC server.
Option 1. - Using the SAS host.keytab file.
# /opt/quest/bin/vastool status
# /opt/quest/bin/vastool ktutil -k /etc/opt/quest/vas/host.keytab -v alias host/ wecsrv.domain.com http/wecsrv.domain.com
# /opt/quest/bin/vastool ktutil -k /etc/opt/quest/vas/host.keytab list
# systemctl restart syslog-ng-wec
Option 2. - Using SAS to create a new keytab file.
# /opt/quest/bin/vastool status
This will create an Active Directory user object in the default ‘Computers’ called “wecsrv-HTTP” with the Service Principal Name (SPN) “HTTP/ wecsrv.domain.com”
It will also create a keytab on the Syslog-ng server, called “HTTP.keytab” in the default location – “/etc/opt/quest/vas/”
# /opt/quest/bin/vastool -u administrator service create HTTP/wecsrv.domain.com@wecsrv.domain.com
# /opt/quest/bin/vastool ktutil -k /etc/opt/quest/vas/HTTP.keytab list
# systemctl restart syslog-ng-wec
© 2025 One Identity LLC. ALL RIGHTS RESERVED. Terms of Use Privacy Cookie Preference Center