Symantec Identity Manager - Unable to log in to Identity Manager: Access Gateway SPS Exception Noodle_ConnectException, Connection refused remotely, no process is listening on the remote address/port.

Products

• CA Identity Manager
• CA Identity Governance
• CA Identity Portal
• CA Identity Suite

Issue/Introduction

When attempting to log into Symantec Identity Manager via the Access Gateway (formerly Secure Proxy Server), users receive a "CA Access Gateway - Error Report" after entering their credentials.

Error Details:

• Request URI: /iam/im/identityEnv/ui7
• Error Type: SPS Exception
• Error Code: Noodle_ConnectException
• Error Message: Connection refused remotely, no process is listening on the remote address/port.

 

Environment

Identity Manager

Siteminder Access Gateway (SPS)

Cause

The error occurs because the Access Gateway cannot establish a connection to the backend Identity Manager server. This is typically due to:

1. The Access Gateway service not running.
2. Incorrect agent configuration within the Identity Manager domain.
3. Network/Firewall restrictions blocking communication between the Access Gateway and the backend server.

Resolution

1. Verify Access Gateway Service Status 

Ensure that the Access Gateway (Secure Proxy Server) service is active. Restart.

2. Validate Domain Agent Configuration 

Confirm that the Identity Manager domains are mapped to the correct active agents:

1. In the SiteMinder Administrative UI, navigate to Policies > Domains.
2. Locate and edit the identityEnvDomain (click the pencil icon).
3. Select the Realms tab.
4. For each realm (e.g., TEWS6, pub, ims):
   • Click Lookup Agent/Agent Group.
   • Select the correct, active agent.
5. Save changes and cycle all relevant components.

3. Inspect Network Connectivity

• Verify that no recent firewall rules or network security groups have been implemented that might block the remote address or port used by the backend Identity Manager server.
• Ensure the backend process is actually listening on the expected port (e.g., use netstat or telnet to test connectivity from the Access Gateway host to the IM host).