Gateway and Single signOn registration

Products

• CA API Gateway

Issue/Introduction

The Gateway and Single SignOn registration has a defect when adding a new policy server. The registration does not populate additional policy servers in the host configuration object. This affects new registration and when re-registration is performed. 

For re-registration if additional policy servers have been added they get removed setting it back to one

see example :

Before the re-Registration

 

The information and values about :

 

Address

Authentication.port

Authorization.port

connection.max

connection.min

connection.step

timeout

 

are present on the screen above.

 

After re-Registration

 

 

Note : The information about :

Address

Authentication.port

Authorization.port

connection.max

connection.min

connection.step

timeout

 

are missed on the screen above. To recover that required info, apply the workaround suggested as a solution.

 

Environment

API Gateway 9.4

Cause

The registration does not populate additional policy servers in the host configuration object. This affects new registration and when re-registration is performed. 

Resolution

The procedure to export the siteminder_configuration_property data table from the mysql ssg db, then restore it after Single Sign On registration configuration.

Dump and restore a single table from .sql Dump :

1. To export the Siteminder config, run this command (this is the dump process you need to run from Linux gateway terminal mode):

mysqldump -u root -p ssg siteminder_configuration_property > ssg.siteminder_configuration_property.sql

2. To restore tables in one line, run this command from the gateway server terminal mode:

mysql -u root -p ssg < ssg.siteminder_configuration_property.sql

This will re-create the data into the siteminder_configuration_property table to have the same data as Before the Registration process.

Additional Information

REF: Create a Ca Single Sign on configuration