No Access Account Error in ESM

Products

• STARTER PACK-7
• CA Rapid App Security
• CA API Gateway

Issue/Introduction

When migrating a policy using ESM, there is a "No Access Account" error when one of the Gateways is selected. Restarting ESM, deleting and re-addeding the Gateway Node, and restarting the Gateway service did not resolve the issue. 

Environment

Release: L7SGA299000-9.0-API Gateway SOA Gateway-HARDWARE APPLIANCE DUAL CPU
Component:

Cause

When viewing this error in the ESM, this means the logged in ESM user isn't mapped to the Gateway it is trying to access.

Resolution

Use the "Map ESM User to Gateway.pdf" to manually map the ESM user to the Gateway.