Migrate to Production of Risk rulesets followed by an "Organization Cache Refresh" may lead to unexpected behavior as "Server Cache Refresh" is required

Products

• CA Strong Authentication

Issue/Introduction

This document informs that CA Risk Authentication related Migrate to Production of risk rule operation(s) followed by an organization related "Refresh Cache" may lead to unexpected behaviors as server related "Refresh Cache" is  required after every "Migrate to production".

Environment

All supported CA Risk Authentication versions

Cause

Migrate to Production of Risk rulesets has a system/server level impact and hence requires a server "Refresh Cache". Organization related "Refresh Cache" does not suffice.

Resolution

Note when a "Migrate to Production" of Riskfort ruleset is performed, the notification message as shown below displays the message "When you configure data for a Ruleset, it is not available for a administration to use unless you make it Active. For this, you must migrate to production. After migrating, you must then refresh the server cache."

So, always perform a server level "Refresh Cache" after ANY "Migrate To Production", as "Migrate To Production" is a server related activity NOT an organization specific activity. 

Example of a  required server level "Refresh Cache" via Admin UI is shown below" ("Services and Server Configurations" ==> Administration Console" ==> "Refresh Cache"  as shown below.

 

 

Additional Information

None.