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

Products

• CA API Gateway
• CA Microgateway

Issue/Introduction

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

Environment

This article applies to all supported Gateway versions.

Cause

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

Resolution

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--