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

book

Article ID: 39071

calendar_today

Updated On:

Products

CA Rapid App Security CA Advanced Authentication CA API Gateway

Issue/Introduction

Question:

 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. SM (State Manager) – arcotsm.log

5. Adaptershim – adaptershim.log on CA Siteminder Policy Server 

 

Answer:

 1.    UDS  (arcotuds.log)

a.       Navigate to <ARCOT_HOME>\conf directory.

b.      Edit udsserver.ini and change “ERROR” to “DEBUG” and “INFO” to “DEBUG”.  The example below is turning debug

 

Before: log4j.rootCategory=ERROR, debuglog

After:  log4j.rootCategory=DEBUG, debuglog

 

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

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

 

 

c.       Restart the Application Server.

 

 

2.    Admin Console  (arcotadmin.log)

a.       Navigate to <ARCOT_HOME>\conf directory.

b.      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.

 

Before: log4j.rootCategory=ERROR, roothandle

After:  log4j.rootCategory=DEBUG, roothandle

 

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

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

 

c.       Restart the Application Server.

 

 

3.    Authentication Flow Manager  (arcotafm.log)

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

a.       Navigate to <ARCOT_HOME>\conf\afm directory.

b.       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.

 

       Advanced Authentication 6.2  and  5.4  releases - (Adapter 2.2.7 and below)

a.       Navigate to <APPLICATION_SERVER_HOME>\webapps\arcotafm\WEB-INF\classes\

 

b.      Edit 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.

 

Before: log4j.rootLogger=INFO, afmout

After:  log4j.rootLogger=DEBUG, afmout

 

Before: log4j.logger.com.arcot.integrations.frontend=INFO

After:  log4j.logger.com.arcot.integrations.frontend=DEBUG

 

c.       Restart the Application Server.

 

 

4.    State Manager  (arcotsm.log)

          Advanced Authentication  7.1 and  above releases.

a.       Navigate to <ARCOT_HOME>\conf\afm directory .

b.      Edit arcotsm-log4j.properties and change “INFO” to “DEBUG” on operations you want to debug.  The example below is turning debug on the front-end State Manager modules.

         Advanced Authentication 6.2  and  5.4  releases.

a.       Navigate to <APPLICATION_SERVER_HOME>\webapps\arcotsm\WEB-INF\classes\

b.      Edit log4j.properties and change “INFO” to “DEBUG” on operations you want to debug and then save.  The example below is turning debug on the front-end State Manager modules.

 

Before: log4j.rootLogger=INFO, afmout

After:  log4j.rootLogger=DEBUG, afmout

 

Before: log4j.logger.com.arcot.integrations.frontend=INFO

After:  log4j.logger.com.arcot.integrations.frontend=DEBUG

 

c.       Restart the Application Server.

  

 

5.    Adaptershim (adaptershim.log on CA Siteminder Policy Server)

a.       Navigate to <ARCOT_HOME>\conf on the CA Siteminder

b.      Edit adaptershim.ini  file and set debug parameter  as such-  “HandleLevel=1”.

c.       Save adaptershhim.ini

d.      The parameter will turn debug on in about 5 minutes; a restart of the CA Siteminder Policy Server is not required.

 

 

Cause

NA

Environment

Release: ARCWFT05900-8-Arcot-WebFort-for Windows
Component:

Resolution

Discussed in Issue/Introduction

Additional Information

None