Existing jar file does not overwritten during policy extension file upload
This document (7012077) is provided subject to the disclaimer at the end of this document.
NetIQ Access Manager 3.2 Access Gateway Policies
Custom policy written using the Policy APIs
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.
and restart the AG tomcat service using '/etc/init.d/novell-mag restart'
This Support Knowledgebase provides a valuable tool for NetIQ/Novell/SUSE customers and parties interested in our products and solutions to acquire information, ideas and learn from one another. Materials are provided for informational, personal or non-commercial use within your organization and are presented "AS IS" WITHOUT WARRANTY OF ANY KIND.
- Document ID:7012077
- Creation Date:04-APR-13
- Modified Date:04-APR-13
- NetIQAccess Manager (NAM)
Did this document solve your problem? Provide Feedback