Running scripts for populating DB tables in new environment
search cancel

Running scripts for populating DB tables in new environment

book

Article ID: 261351

calendar_today

Updated On:

Products

CA Identity Suite

Issue/Introduction

We are setting brand new environment 14.4 but we did the silent install and when it started it was pointing to dummy DB and now we are pointing to actual DB, our senior tech and DB senior tech advised that it should be populating itself but it didn't ran on its own and now we are looking for the scripts to run it along with explanation what actions are performed on any steps so we can edit it accordingly to our data base and schemas.

This is not V app, it is a standalone installation of 14.4 CP-1. we have CHF-1 & CHF-2 applied.

Below are the links we referred and path to the older scripts we have.

\CA\Identity Manager\IAM Suite\Identity\tools\db, other than the snapshot database.  You can get details on this process in the documentation here:
https://techdocs.broadcom.com/us/en/symantec-security-software/identity-security/identity-manager/14-4/installing/separate-database-configuration-optional.html

Environment

Release : 14.4

Resolution

This issue came down to the fact that the authentication filter was enabled, but the IDM_Auth table was not created or populated

We followed the steps here:

https://techdocs.broadcom.com/us/en/symantec-security-software/identity-security/identity-manager/14-4/configuring/security.html

Steps 2-5 Under the heading of:

Protect an Existing Environment After Upgrade
After you upgrade to 
Identity Manager
 12.6 or above, you can protect the Management Console using native security.
 
After this, the customer was using FIPS in this environment and had to use the pwdtools command as follows:
 pwdTools -FIPS -p <plain text> -k <FIPS key file path>
 
Non fips environments would use:
 
pwdtools -JSAFE  -p <plain text>