Existing jar file does not overwritten during policy extension file upload

  • 7012077
  • 04-Apr-2013
  • 04-Apr-2013

Environment

NetIQ Access Manager 3.2
NetIQ Access Manager 3.2 Access Gateway Policies
Custom policy written using the Policy APIs

Situation

Customer created a custom policy on the AG using the Policy APIs. After importing the policy 
extension jar in the NAM UI and creating a policy using this, all worked fine. Some basic changes
were made to the JAR file, and the admin tried to re-upload it.

Uploading with the "overwrite existing *.jar file" option seemed to work but the new changes did not seem to be reflected
in the policy evaluation. After checking, it appears that the overwrite option failed in that the
original jar file is still running on the system. Steps to duplicate: - Upload a.jar in policy - extension in NAM - Now modify some code (Deny message / url) and recreate jar again with same name i.e. a.jar - Upload this new jar in system with option selected as "Overwrite existing *.jar file" - Refresh system and access protected resource and verify the behavior. Expected Result: New changes in policy should be effective. And pick up by ag Actual Result: New changes doesn't come into effect.

Resolution

Manually copy the new jar file to the following location:

/opt/novell/nesp/lib/webapp/WEB-INF/lib

and restart the AG tomcat service using '/etc/init.d/novell-mag restart'

Feedback service temporarily unavailable. For content questions or problems, please contact Support.