ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.

API Gateway: Error observed - "Assertion not available: Code not available for assertion: CustomAssertion"


Article ID: 145204


Updated On:


CA API Gateway CA Microgateway


This article will discuss the issue of "Assertion not available: Code not available for assertion: CustomAssertion", which is typically related to a permissions issue on the AAR or JAR file in the API Gateway. 

Example error in SSG logs: 

2020-02-14T10:43:11.801-0800 SEVERE  353 com.l7tech.server.SoapMessageProcessingServlet: Assertion not available: Code not available for assertion: CustomAssertion


This is typically caused by permissions on the assertion jar file.


This article applies to all supported Gateway versions.


To resolve this issue, follow the steps below:
  1. Locate the affected assertion by navigating to /opt/SecureSpan/Gateway/runtime/modules/lib
    • Finding the affected assertion is a bit of trial and error, but but usually it is found by simply looking for which assertions have permissions of rw------- instead of rw-r--r--
  2. Ensure all permissions are rw-r--r--