Environment
NetIQ Access Manager 3.2 Support Pack 1 Interim Release 1
NetIQ Access Manager 3.2 Access Gateway Service and Appliance has problem
SNAM enabled auditing enabled on Access Gateway
NetIQ Access Manager 3.2 Access Gateway Service and Appliance has problem
SNAM enabled auditing enabled on Access Gateway
Situation
Access Manager setup and working fine - users can access protected resources behind the Access Gateway (AG) after having successfully authenticated at the Identity (IDP) Server. The IDP server audits all events to the Audit server, but the Access Gateway generates an email to the Administrator when an audit event occurs.
For example, the Access Gateway auditing is setup via AG Devices > Access Gateways > Edit > Alerts > [Name of Profile] where alerts are enabled for the following events:
System Up , System Down , Configuration Changed
All worked well before 3.2 SP1 IR1 was applied, but after applying the patch the administrator failed to receive any audit events via email anymore. Looking at the ags_error.log file under /var/opt/novell/nam/logs/mag/amlogging/, the following exception was logged with every corresponding audit event:
<amLogEntry> 2013-02-08T10:39:47Z ERROR AGM: AM#204653001: AMDEVICEID#ag-68447E157B36F281: AgmAlertIndication: processIndication(), thread=1901, Exception Caught: java.lang.NoSuchMethodError: com.novell.nacm.logging.alert.AMAlertLog.email(Ljava/lang/String;Ljava/lang/String;Ljava/lang/String;Ljava/lang/String;Ljava/lang/String;)V </amLogEntry> <amLogEntry> 2013-02-08T10:39:47Z ERROR AGM: AM#204653001: AMDEVICEID#ag-68447E157B36F281: AgmAlertIndication: java.lang.NoSuchMethodError: com.novell.nacm.logging.alert.AMAlertLog.email(Ljava/lang/String;Ljava/lang/String;Ljava/lang/String;Ljava/lang/String;Ljava/lang/String;)V at com.novell.nacm.agm.AgmAlertIndication.processIndication(AgmAlertIndication.java:179) at com.novell.dcc.channel.RespondChannel$_B.call(Unknown Source) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) at java.util.concurrent.FutureTask.run(FutureTask.java:138) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:662) </amLogEntry>
This caused the failure to send the email.
For example, the Access Gateway auditing is setup via AG Devices > Access Gateways > Edit > Alerts > [Name of Profile] where alerts are enabled for the following events:
System Up , System Down , Configuration Changed
All worked well before 3.2 SP1 IR1 was applied, but after applying the patch the administrator failed to receive any audit events via email anymore. Looking at the ags_error.log file under /var/opt/novell/nam/logs/mag/amlogging/, the following exception was logged with every corresponding audit event:
<amLogEntry> 2013-02-08T10:39:47Z ERROR AGM: AM#204653001: AMDEVICEID#ag-68447E157B36F281: AgmAlertIndication: processIndication(), thread=1901, Exception Caught: java.lang.NoSuchMethodError: com.novell.nacm.logging.alert.AMAlertLog.email(Ljava/lang/String;Ljava/lang/String;Ljava/lang/String;Ljava/lang/String;Ljava/lang/String;)V </amLogEntry> <amLogEntry> 2013-02-08T10:39:47Z ERROR AGM: AM#204653001: AMDEVICEID#ag-68447E157B36F281: AgmAlertIndication: java.lang.NoSuchMethodError: com.novell.nacm.logging.alert.AMAlertLog.email(Ljava/lang/String;Ljava/lang/String;Ljava/lang/String;Ljava/lang/String;Ljava/lang/String;)V at com.novell.nacm.agm.AgmAlertIndication.processIndication(AgmAlertIndication.java:179) at com.novell.dcc.channel.RespondChannel$_B.call(Unknown Source) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) at java.util.concurrent.FutureTask.run(FutureTask.java:138) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:662) </amLogEntry>
This caused the failure to send the email.
Resolution
Apply the 3.2 SP1 IR1a patch.
Cause
One of the jar files that included the required method was not included with the original patch.