Product Documentation

This document provides information that should be collected from both (DEV/UAT as well as PROD) clusters and provided to StrongKey in order to plan the migration process.

 

KeyAppliance Current Status

The following steps provide the process to collect information to understand the current state of the SAKA cluster.

  1. Log into the appliance as root user.
  2. Execute Health Check script which would collect software stack and OS configuration details.
    shell> cd /usr/local/software/saka
    shell> ./SAHC.sh
    https://demo4.strongkey.com/getstarted/assets/documents/HTML/images/key_strong_cyan.pngNOTE: This should create a zip file under /tmp directory. Please send us that file.

     

  3. Log out of root user.
  4. Log into the appliance as strongauth user.
  5. Execute ping service to collect the current version details.
    shell> pingsaka.sh 1 
    https://demo4.strongkey.com/getstarted/assets/documents/HTML/images/key_strong_cyan.pngNOTE: This will prompt for a password and you would need to provide the password for pinguser of DID-1. If not changed, default should be: Abcd1234!


  6. Collect DB table details to understand the size and allocation of the data.
    shell> mysql -u skles -p`dbpass 2> /dev/null` strongkeylite -e "source /usr/local/software/saka/verify-counts.sql;"
    shell> mysql -u skles -p`dbpass 2> /dev/null` strongkeylite -e "select sid, did, count(*) from encryption_requests group by sid, did;"
    shell> mysql -u skles -p`dbpass 2> /dev/null` strongkeylite -e "select sid, did, hmac_keyalias,count(*) from encryption_requests group by sid, did, hmac_keyalias;"