Installation and Upgrade Guides › Policy Server Installation Guide › Troubleshooting › Policy Store Troubleshooting › SSL initialization failed: error -8174 (security library: bad database.)

SSL initialization failed: error -8174 (security library: bad database.)

Valid on Windows and UNIX Systems

Symptom:

When I run smldapsetup ldmod -fpstore -ssl1 -c/app/siteminder/ssl/cert7.db for policy stores that are using an SSL-encrypted connection to Oracle Directory Server (formerly Sun Directory Server Enterprise Edition), I receive the following error message:

"SSL initialization failed: error -8174 (security library: bad database.)"

Solution:

1. Make sure the key3.db file exists in the same directory as cert7.db for the Netscape Web browser.
2. Rerun this smldapsetup command, and, for the -c option, specify the path of the directory where the SSL client certificate database file, cert7.db, exists.

   Example: if cert7.db exists in /app/siteminder/ssl, specify -c/app/siteminder/ssl/cert7.db

More Information:

smldapsetup

ODBC Policy Store Import Fails with UserDirectory Error

Symptom:

I receive an error message stating that the policy store failed operation "save" for object type "UserDirectory" when importing policy store data into an ODBC policy store.

Solution:

It is possible that the server name in the ODBC store's userDirectory object is longer than 512 characters, which by default, exceeds the limit allowed by the MS SQL Server and Oracle policy store schema scripts that are shipped with SiteMinder.

Do one of the following:

If you are trying to import policy data into a supported version of a MS SQL Server policy store:

1. Open sm_mssql_ps.sql.

   Note: This schema script is located in policy_server_home\db\SQL.

2. Search for the following text:

   CREATE TABLE smuserdirectory5

3. Modify "server smstringreq512N," to one of the following depending on your needs:
   • server smstringreq1024,N
   • server smstringreq4000,N
4. Re-import the policy store schema into the policy store.
5. Import the policy store data.

If you are trying to import policy data into a supported version of an Oracle policy store:

1. Open sm_oracle_ps.sql.

   Note: This schema script is located in policy_server_home\db\SQL.

2. Search for the following text:

   CREATE TABLE smuserdirectory5

3. Modify "server VARCHAR2(512) NOT NULL," to one of the following depending on your needs:
   • server VARCHAR2(1024) NOT NULL,
   • server VARCHAR2(4000) NOT NULL,
4. Re-import the policy store schema into the policy store.
5. Import the policy store data.