STDOUT DD information in MFASTC disappears after maintenance

Products

• Advanced Authentication Mainframe

Issue/Introduction

Prior to applying AAM maintenance,  the STDOUT DD in MFASTC provided trace data useful for debugging, but this is no longer produced.  

An example of the output: 

2022-08-01 12:29:54,286 ThreadID:14 -- setting userName from JNI = 'usr00001'... 

2022-08-01 12:29:54,287 ThreadID:14 -- setting password from JNI; length =    '8'...                                           

2022-08-01 12:29:54,287 ThreadID:14 -- setting hostName from JNI = '122.332.5556.170'...                  

2022-08-01 12:29:54,288 ThreadID:14 -- setting shared secret from JNI; length ='14'...      

2022-08-01 12:29:54,288 ThreadID:14 -- setting authPort from JNI = '2508'...                                                 

2022-08-01 12:29:54,288 ThreadID:14 -- setting acctPort from JNI = '1813'...                                                       

2022-08-01 12:29:54,289 ThreadID:14 -- Exiting parseRadiusDataObject...dataItems:com.ca.security.mfa.jni.service.MfaServiceDataItems@6E33112          

2022-08-01 12:29:54,289 return code for TOKEN_GET = 0                                                                               

2022-08-01 12:29:54,289 ThreadID:14<***>RADIUS_REQUEST received... processing...  <***>          

2022-08-01 12:29:54,290 Entered MFAPutReqInfo(...) for RADIUS requests             

2022-08-01 12:29:54,293 Going into receive code                                                                                    

2022-08-01 12:29:54,293 Entering MFADispatchActor Actor onReceive, message type: class com.ca.security.mfa.akka.messages.MFAPutReqInfo                              

                                                             

                                                                                        

 

Environment

Release : 2.0

Component : Advanced Authentication Mainframe

Cause

If the customer had previously set the level for MFA_STDOUT in logback.xml, in rare instances maintenance may have overwritten this customization.

Resolution

The details on tracing are in our doc on this page under the sub-title

(Optional) Configure Tracing for the Advanced Authentication Mainframe Java Component

Configure tracing by updating logback.xml in /MFASTC/directory if needed. logback.xml is an ASCII file and must be updated in ASCII format. Review the following options and update if desired.

<root level="INFO"> Determines the log level. The five levels are (ERROR, WARN, INFO, DEBUG, and TRACE). These levels are in order from the least amount of information logged (ERROR) to the most (TRACE). Default: INFO

<file> Contains the path and the name of the file to which the log data is sent. Default:  FASTC/directory/logs

<FileNamePattern> Determines where to archive log files and the name format. The default path is MFASTC/directory/logs. (%i is the index where the index ranges from what is specified by

<MinIndex> and <MaxIndex>.) The default values of <MinIndex> and <MaxIndex> are 1 and 20 respectively.

<MaxFileSize> Specifies how large the file can get before the file resets and archives. Default: 50 MB