000033429 - How to turn on debug logging to troubleshoot AFX connectors in versions 7.0.0, 6.9.1 and 6.8.1 of RSA Identity Governance & Lifecycle

Document created by RSA Customer Support Employee on Jun 28, 2016Last modified by RSA Customer Support on Apr 16, 2020
Version 5Show Document
  • View in full screen mode

Article Content

Article Number000033429
Applies ToRSA Product Set: RSA Identity Governance & Lifecycle 
RSA Version/Condition: 6.8.1, 6.9.1, 7.0.0
IssueDebug logging is extremely useful and informative for troubleshooting RSA Identity Governance & Lifecycle AFX connectors. This article describes the steps to enable AFX connector debug logging in RSA Identity Governance & Lifecycle version 7.0.1 and higher.

There is quite a bit of logging output into the following AFX logs but it generally does not provide the level of detail required to troubleshoot a specific AFX connector. These logs are:
  • $AFX_HOME/mule/logs/mule_ee.log
  • $AFX_HOME/mule/logs/mule.AFX-MAIN.log
Log output for connector-specific issues is logged to a connector-specific AFX log file of the format:

The information logged to these connector-specific log files can be very useful when troubleshooting specific AFX connector issues. The amount of logging that is written to these connector-specific logs is controlled by two flags: INFO and DEBUG. By default the INFO flag is enabled. To log additional data to a connector-specific log file, the DEBUG flag can be enabled. 


NOTE: The connector_name is the name of the connector which correlates to a name column in an internal database table. This name may or may not be the same as the display name seen in the RSA Identity Governance & Lifecycle user interface under AFX > Connectors
To enable connector-specific debug logging, perform the following steps as the afx user. In this example, the display name of the connector name is Active Directory Connector and the name of the connector log file is $AFX_HOME/mule/logs/mule.AFX-CONN-Active_DirectoryConnector.log.

  1. Edit the $AFX_HOME/mule/apps/AFX-CONN-<connector_name>/classes/log4j.xml file to change the log level from INFO to DEBUG. In this example the filename is: $AFX_HOME/mule/apps/AFX-CONN-Active_DirectoryConnector/classes/log4j.xml.

cd $AFX_HOME/mule/apps/AFX-CONN-Active_DirectoryConnector/classes
vi log4j.xml

  1. Edit the .xml using the following syntax: 

<logger name="org.mule.api.processor.LoggerMessageProcessor"> 
<!-- <level value="INFO"/> --> 
<level value="DEBUG"/> 

  1. For the changes to take effect immediately, touch the file $AFX_HOME/mule/apps/AFX-CONN-<connector_name>/mule-config.xml file. In this example the file location is: $AFX_HOME/mule/apps/AFX-CONN-Active_DirectoryConnector/mule-config.xml.

cd $AFX_HOME/mule/apps/AFX-CONN-Active_DirectoryConnector
touch mule-config.xml

WARNING: Do NOT restart the AFX server or edit the AFX connector in the user interface, as these actions will override the debug settings just made. 

  1. The next time you use the connector (or test the connector capabilities), you will see the debug output in the $AFX_home/mule/logs/mule.AFX-CONN-<connector_name>.log. For example, $AFX_HOME/mule/logs/mule.AFX-CONN-Active_DirectoryConnector.log.

To enable debug logging in 7.0.1 or higher, please see RSA Knowledge Base Article 000030219 -- How to turn on debug logging to troubleshoot AFX connectors in versions 7.0.1 and higher of RSA Identity Governance & Lifecycle.
NotesHere is an example of adding an account to an AD group with debug enabled.

019-10-21 15:13:28.327 [DEBUG] org.mule.api.processor.LoggerMessageProcessor:121 - XML Payload from JMS:
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<Envelope xmlns="http://aveksa.com/afx/messages/primary">
        <Request timestamp="2019-10-21T15:13:20.674-04:00" id="1">
            <verb name="AddAccountToGroup">
                    <parameter name="Account">CN=Book\, Rita,OU=SE,OU=vcloud Users,DC=2k8r2-vcloud,DC=local</parameter>
                    <parameter name="Group">CN=G1,OU=vcloud Users,DC=2k8r2-vcloud,DC=local</parameter>
            <Response timestamp="2019-10-21T15:13:28.299-04:00">