Configure the keystore to authenticate the server certificate - Connect_CDC - aws_mainframe_modernization_service - connect_cdc_mimix_share - Latest

You can use the default Java keystore to preform authentication.

1. On the machine running Connect CDC Director, create a Java keystore.

   1. Open a command console session.

   2. At the command prompt, type

      'keytool -genkey -keyalg RSA -alias empty -keystore {name of keystore - e.g. precisely.jks}'

             and press enter to create keystore with one entry.

   3. Type a password when prompted.

   4. Accept 'UNKNOWN' when prompted for CN, ORG, CITY, etc.

   5. Type 'yes' at the 'Is this entry correct?' prompt.

   6. At the command prompt, type

   'keytool -delete -alias empty -keystore oracyberark2.jks'

          and press enter to remove the key and empty the keystore.

2. Export the trusted certificate from SQL Server.

   1. Launch Microsoft Management Console (MMC) and connect to the SQL server.

   2. Navigate to the trusted certificate, by either selecting 'Certificates (Local Computer)' -> Personal -> Certificates or selecting 'Certificates (Local Computer)' -> 'Trusted Root Certification Authorities' -> Certificates.

   3. Right-click on the trusted certificate used by SQL Server and select 'All Tasks' -> Export to open the export wizard.

   4. Accept most of the default values in the Wizard. For page to specify file for certificate, type the file system path to which you save the trusted file certificate file on the machine running Connect CDC Director.

3. On the machine running Connect CDC Director, at the command prompt, type

   'keytool -import -keystore {name of empty keystore from step 1} 
   					-file {name of trusted certificate file from step 2}'

          and press enter to add the trusted certificate to the keystore.

4. Type 'yes' at the 'Trust this certificate?' prompt.