Tactical Assertions gets migrate as part of running the ansible upgrade scripts?
search cancel

Tactical Assertions gets migrate as part of running the ansible upgrade scripts?

book

Article ID: 193590

calendar_today

Updated On:

Products

CA API Gateway API SECURITY CA API Gateway Precision API Monitoring Module for API Gateway (Layer 7) CA API Gateway Enterprise Service Manager (Layer 7) STARTER PACK-7 CA Microgateway

Issue/Introduction

The custom tactical assertions gets migrate as part of running the Ansible upgrade scripts?

I’m not able to see the “Remote cache” assertion in the newly migrated v10 Gateway but its present in our 9.4 gateway

Environment

Release : 9.4

Component : API GATEWAY

Resolution

Tactical assertions will not be migrated as part of Ansible upgrade.

1. You will need to confirm the compatibility with the Tactical Assertion and the Target Gateway 10 version first
2. after confirmed you can include/install the assertion file directly in your target Gateway for use it by following the same instructions
for installing it that you would have for the source Gateway node.

ie : Some Supported Tactical Assertions in Gateway 10

AsymmetricKeyEncryptionDecryption
FastResolveServiceAssertion
GatewayMetrics
GenerateSecuritySignature
InjectionFilter
ExtensibleSocketConnector
LogMessageToSysLog
RemoteCache
SNMPAgent
SymmetricKeyEncryptionDecryption
ValidateSecuritySignatureAssertion
WssSignatureKeyReference
XACMLPolicyDecisionPoint