How to enable Syslog Server on SecurID Access Prime running on Linux
Originally Published: 2020-06-22
Article Number
Applies To
RSA Version/Condition: 1.8.x
Platform: Linux
Platform (Other): null
O/S Version: null
Product Name: null
Product Description: null
Issue
Tasks
Resolution
NOTE: Change the IP Address 10.222.247.34 to your syslog server's IP Address.
*** AMIS
vi /opt/rsa/primekit/configs/amis/tomcat-amis/setenv.sh
export CATALINA_OPTS="$CATALINA_OPTS -Dsyslog.server=10.222.247.34"
*** SSP
vi /opt/rsa/primekit/configs/ssp/tomcat-ssp/setenv.sh
export CATALINA_OPTS="$CATALINA_OPTS -Dsyslog.server=10.222.247.34"
*** HDAP
vi /opt/rsa/primekit/configs/hdap/tomcat-hdap/setenv.sh
export CATALINA_OPTS="$CATALINA_OPTS -Dsyslog.server=10.222.247.34"
2) Edit and set the following xml files as following:
*** AMIS
vi /opt/rsa/primekit/configs/amis/am8-logconfig.xml
IMPORTANT: Make sure the syslog.server variable is set.
<param name="syslogHost" value="${syslog.server}"/>
<param name="syslogHost" value="${syslog.server}"/>
IMPORTANT: Make sure the AM8_AUDIT_SYSLOG is not commented as showing below:
<logger name="com.rsa.ucm.am8.audit" additivity="false">
<level value="INFO"/>
<appender-ref ref="AM8_AUDIT_daily"/>
<appender-ref ref="AM8_AUDIT_SYSLOG"/>
</logger>
Use the following screenshot as reference.
*** SSP
vi /opt/rsa/primekit/configs/ssp/config/logconfig.xml
IMPORTANT: Make sure the syslog.server variable is set.
<param name="syslogHost" value="${syslog.server}"/>
IMPORTANT: Make sure the SSP_AUDIT_SYSLOG is not commented.
<logger name="audit.com.rsa.pso" additivity="false">
<level value="INFO" />
<appender-ref ref="SSP_AUDIT_daily" />
<appender-ref ref="SSP_AUDIT_SYSLOG" /> -->
</logger>
Use the following screenshot as reference.
*** HDAP
vi /opt/rsa/primekit/configs/hdap/config/laplogconfig.xml
IMPORTANT: Make sure the syslog.server variable is set.
<param name="syslogHost" value="${syslog.server}"/>
<param name="syslogHost" value="${syslog.server}"/>
IMPORTANT: Make sure the HDAP_AUDIT_SYSLOG is not commented.
<logger name="audit.com.rsa.pso" additivity="false">
<level value="INFO"/>
<appender-ref ref="HDAP_AUDIT_daily"/>
<appender-ref ref="HDAP_AUDIT_SYSLOG"/>
</logger>
Use the following screenshot as reference.
3) Restart all SecurID Access Prime Services.
cd /opt/rsa/primekit/scripts
./ssp_shutdown.sh
./hdap_shutdown.sh
./amis_shutdown.sh
./amis_startup.sh
./ssp_startup.sh
./hdap_startup.sh
Related Articles
RSA Identity Governance and Lifecycle error in ACM-57594.sql during migration from 6.8.1 to 7.0.1 where workflows have sim… 53Number of Views Online video tutorial reference for the RSA SecurID Suite 113Number of Views Linux Kernel vulnerability CVE-2017-17806 on RSA Appliance 3Number of Views Installation fails with 'Reference data is not available for verifying prerequisites on this operating system distributio… 37Number of Views How to migrate the RSA enVision platform from Windows 2003 to 2008 without affecting the data on the DAS 2000 17Number of Views
Trending Articles
RSA Authentication Manager Upgrade Process RSA Release Notes for RSA Authentication Manager 8.8 RSA RADIUS Server service failed to start in the RSA Authentication Manager 8.1 Operations Console Microsoft Entra ID External MFA - Relying Party Configuration Using OIDC - RSA Ready Implementation Guide RSA Release Notes: Cloud Access Service and RSA Authenticators
Don't see what you're looking for?