How do I turn on DEBUG for CA Strong Authentication Java components ?
search cancel

How do I turn on DEBUG for CA Strong Authentication Java components ?

book

Article ID: 39071

calendar_today

Updated On:

Products

CA Advanced Authentication CA Strong Authentication CA Risk Authentication

Issue/Introduction

How do I turn “Debug ON” on Advanced Authentication Java components such as:

  1. UDS (User Data Service) – arcotuds.log
  2. Admin Console – arcotadmin.log
  3. AFM (Authentication Flow Manager) – arcotafm.log
  4. Adaptershim – adaptershim.log on CA Siteminder Policy Server 

Environment

Release: 9.x

Cause

NA

Resolution

UDS  (arcotuds.log)

  1. Navigate to <ARCOT_HOME>\conf directory.
  2. Edit udsserver.ini and change “ERROR” to “DEBUG” and “INFO” to “DEBUG”.  The example below is turning debug
  3. Restart the Application Server.

Before: log4j.rootCategory=ERROR, debuglog

After:  log4j.rootCategory=DEBUG, debuglog

Before: log4j.logger.com.arcot.euds=INFO

After:  log4j.logger.com.arcot.euds=DEBUG

Admin Console  (arcotadmin.log)

  1. Navigate to <ARCOT_HOME>\conf directory.
  2. Edit adminserver.ini and change “ERROR” to “DEBUG” and “INFO” to “DEBUG” on operations you want to debug.  The example below is turning debug on the UDS modules that Admin interacts with.
  3. Restart the Application Server.

 

Before: log4j.rootCategory=ERROR, roothandle

After:  log4j.rootCategory=DEBUG, roothandle

Before: log4j.logger.com.arcot.euds=INFO

After:  log4j.logger.com.arcot.euds=DEBUG

Authentication Flow Manager  (arcotafm.log)

          Advanced Authentication  7.1 and  above releases - (Adapter 2.2.9 and above)

  1. Navigate to <ARCOT_HOME>\conf\afm directory.
  2. Edit arcotafm-log4j.properties and change “INFO” to “DEBUG” on operations you want to debug then save. The example below is turning debug on the front-end Authentication Flow Manager modules.

Adaptershim (adaptershim.log on CA Siteminder Policy Server)

  1. Navigate to <ARCOT_HOME>\conf on the CA Siteminder box.
  2. Edit adaptershim.ini  file and set debug parameter  as such-  “HandleLevel=1”.
  3. Save adaptershhim.ini
  4. The parameter will turn debug on in about 5 minutes; a restart of the CA Siteminder Policy Server is not required.

 

Additional Information

None

Powered by Wolken Software