Connector troubleshooting
Sometimes it is difficult to assess whether the root of a problem is at the ICF or connector level, or at the application level.
If you are using ICF connectors with IDM, you can adjust the log levels for specific parts of the system in the path/to/openidm/conf/logging.properties
file.
The ICF API sets the LoggingProxy at a very high level. You can consider the Logging Proxy as the border between the application (IDM) and the ICF framework.
To start a troubleshooting process, you should therefore enable the Logging Proxy and set it at a level high enough to provide the kind of information you need:
org.identityconnectors.framework.impl.api.LoggingProxy.level=FINEorg.identityconnectors.framework.impl.api.LoggingProxy.level=DEBUG#Enable the LoggingProxy
org.identityconnectors.framework.impl.api.LoggingProxy.level=FINE
#Select the operation you want to trace, to trace all add:
org.identityconnectors.framework.api.operations.level=FINE
#To trace only some:
org.identityconnectors.framework.api.operations.CreateApiOp.level=FINE
org.identityconnectors.framework.api.operations.UpdateApiOp.level=FINE
org.identityconnectors.framework.api.operations.DeleteApiOp.level=FINEThe complete list of operations that you can trace is as follows:
AuthenticationApiOp
CreateApiOp
DeleteApiOp
GetApiOp
ResolveUsernameApiOp
SchemaApiOp
ScriptOnConnectorApiOp
ScriptOnResourceApiOp
SearchApiOp
SyncApiOp
TestApiOp
UpdateApiOp
ValidateApiOpTo enable logging in the remote Java Connector Server, edit the xml configuration file /lib/framework/logback.xml to uncomment the following line:
<logger name="org.identityconnectors.framework.impl.api.LoggingProxy" level="DEBUG" additivity="false">
<appender-ref ref="TRACE-FILE"/>
</logger>To enable logging in the remote .NET Connector Server, edit the configuration file ConnectorServer.exe.config
, setting the following value to true
<add key="logging.proxy" value="false"/>