How do the SSO priorities work?

Document ID : KB000094246
Last Modified Date : 22/05/2018
Show Technical Document Details
Introduction:
The SsoConfig.exe utility updates the mysql tables below:
reporter.performance_center_properties on the NFA console
netqosportal.performance_center_properties on the CAPC server

This document explains the contents of these tables and how priorities work.
Environment:
NFA 9.3.*
CAPC 3.*
Instructions:
The performance_center_properties table contains 3 set of values assigned to the priority column, 0 , 1 and 2 .

The SSOservice uses the existing values with the higher priority .
(If no priority 2 value , it is using the priority 1 value ; if none , the priority 0 value )

Priority 0 corresponds to default values .
Priority 1 corresponds to Remote Values that will be pushed down to all data sources from CAPC.
Priority 2 corresponds to Local Override values at the data source which will overwrite the Remote Values pushed down from CAPC. Or if set in CAPC it will not be pushed down to any data source                       and will only impact CAPC.

To forward CAPC SSO values to all defined Data Sources , you must define some priority 1 or Remote Vavalues in CAPC updating the remote values in the CAPC SsoConfig Utility, in the /opt/CA/PerformanceCenter/ directory.

Then a Data Source synchronization will push the CAPC priority 1 values to the Data Source (NFA , spectrum, ..).

If there is no priority 1 records in CAPC , the Data Source synchronization pushes the CAPC priority 0 values to the Data Sources priority 1 records .

To bypass the priority 0 or 1 values coming from CAPC , you must create some priority 2 values using the SsoConfig.exe utility to Local Override options on each Data Source .

An SSO product  not defined in CAPC will have only priority 0 values in the table performance_center_properties .