Incorrect Instance status showing for Symantec Strong Authentication and Symantec Risk Authentication servers

Products

• CA Advanced Authentication - Strong Authentication (AuthMinder / WebFort)
• CA Strong Authentication
• CA Rapid App Security
• CA Risk Authentication
• CA Advanced Authentication
• CA Advanced Authentication - Risk Authentication (RiskMinder / RiskFort)

Issue/Introduction

Incorrect instance status shown for Symantec Strong Authentication and/or Symantec Risk Authentication instances for example both instances are shown as down but these instances are found processing without any issue. All operations like Refresh Cache, Restart of Symantec Strong Authentication and Symantec Risk Authentication services continue to work but Admin Console shows an incorrect instance status (say as "Failed").

Environment

Release : All Supported AA Releases

Component : Symantec Strong Authentication, Symantec Risk Authentication.

Cause

This is a display only issue where Admin is unable to access the instance to get the status of instance for display.

Resolution

The Admin UI application requires the following Server Management ports to be open to retrieve the instance status (For Risk Case Management, Risk Authentication and Strong Authentication servers) correctly.

a. Port 7780

b. Port 7980

c. Port 9743

a. Port 7780 (Risk Case Management server listens on Port 7780)

b. Port 7980 (Risk Authentication server listens on Server Management Port 7980)

c. Port 9743 (Strong Authentication server listens on Server Management Webservices Port 9743)

https://techdocs.broadcom.com/us/en/symantec-security-software/identity-security/advanced-authentication/9-1/building/ca-strong-authentication-reference-materials/strong-authentication-default-port-numbers.html