Customize password hashes for rescue script

Current Situation

• Consider the linked article about a situation when rescue after loss of access to JOC Cockpit is required.
• In this situation the JETTY_HOME/db/<dbms>identity_service_rescue.sql script can be executed via the JETTY_HOME/install/joc_install_tables.sh|.cmd script.
  • The identity_service_rescue.sql script includes the hashed password for the initial account root using the password root.
• Users would like to customize the hashed password from the rescue script.

Desired Behavior

• The Identity Service management script JETTY_HOME/install/joc_manage_identity_service.sh|.cmd allows to create a hashed password:
  • A personal password is specified like this:
    • joc_manage_identity_service.sh hash secret
    • joc_manage_identity_service.cmd hash secret
  • the hashed password
    • is displayed from the script
    • can be applied by users who want to update the JETTY_HOME/db/<dbms>identity_service_rescue.sql script. It is recommended that users create a copy of this script and store the copy with a different location as the file would be overwritten by a later installation/update of JOC Cockpit. Users will easily identify the hashed default password in this script and can replace the hash value by the output of the management script.
• The database object installer script JETTY_HOME/install/joc/install_tables.sh|.cmd allows to execute an individual rescue script:
  • Examples
    • joc_install_tables.sh rescue /home/sos/identity_service_rescue.sql
    • joc_install_tables.cmd rescue C:\tmp\my_rescue.sql