RSA Version/Condition: 4.2 SP1
Once the fim-deploy.sh script executes successfully, update the catalina.properties file, common.loader property, load the fim.jar, followed by all FIM related jars as mentioned below.
common.loader=${catalina.base}/lib,${catalina.base}/lib/*.jar,${catalina.home}/lib,${catalina.home}/lib/*.jar,${catalina.home}/FIM/lib/fim.jar,${catalina.home}/FIM/lib/*.jar.
But the deployment script already edited the properties file with this string:
common.loader=${catalina.base}/lib,${catalina.base}/lib/*.jar,${catalina.home}/lib,${catalina.home}/lib/*.jar,${catalina.home}/FIM/lib/*.jar
What is the correct setting?
common.loader=${catalina.base}/lib,${catalina.base}/lib/*.jar,${catalina.home}/lib,${catalina.home}/lib/*.jar,${catalina.home}/FIM/lib/fim.jar,${catalina.home}/FIM/lib/*.jar
This is to ensure that the fim.jar gets loaded first and correctly.
Related Articles
Face ID is not recognized using Android Securid 4.1.6.2 10Number of Views Add access unsuccessful due to PS CR behavior in RSA Identity Governance & Lifecycle 63Number of Views Prime kit tomcat.pid: Permission denied error when restarting services for RSA Authentication Manager Prime Kit 91Number of Views Intermittent authentication issue with RSA Authentication Agent 7.4.3 for Windows 55Number of Views SA: puppet agent -t shows rabbitmq permission issues post upgrade or installation of packages. 36Number of Views
Trending Articles
Passwordless Authentication in Windows MFA Agent for Active Directory – Quick Setup Guide RSA Authentication Manager 8.9 Release Notes (January 2026) RSA Authentication Manager Upgrade Process RSA Authentication Manager 8.7 SP2 Setup and Configuration Guide An example of SSO using SAML and ADFS with RSA Identity Management and Governance 6.9.x