Previous Topic: Old Values set for CA Risk Authentication, CA Strong Authentication, Case Management Instance-specific Configurations cannot be Preserved Post Upgrade on Upgrade to New Server MachineNext Topic: Linux rh6 Uninstallation Points to Wrong Location of Log Files

CA Advanced Authentication Release Notes › Known Issues › Risk Authentication Known Issues › Issue in CA Risk Authentication Instances and CA Risk Authentication New Server Name Post Upgrade to 8.0

Issue in CA Risk Authentication Instances and CA Risk Authentication New Server Name Post Upgrade to 8.0

Symptom:

For CA Risk Authentication Connectivity the CA Risk Authentication server is showing old system name instead of new server, and there is no active instance under CA Risk Authentication Instances, post Upgrade to 8.0.

Solution:

Change the server name in CA Strong Authentication and CA Risk Authentication Connectivity from CA Advanced Authentication, to the new server name. This displays the new server instance to appear in the CA Risk Authentication Instance Management. Save and refresh cache.