Make SQL rescue scripts compatible to changes of Identity Services

Current Situation

• The SQL rescue scripts are explained from JS7 - Rescue in case of lost access to JOC Cockpit
• The scripts are broken for use with release 2.5.4 and 2.6.2 as they do not reflect changes to Identity Services
• The wrong SQL statement is

  EXECUTE
  'INSERT INTO IAM_IDENTITY_SERVICES("ID","IDENTITY_SERVICE_TYPE", "IDENTITY_SERVICE_NAME","REQUIRED","DISABLED", "AUTHENTICATION_SCHEME","SINGLE_FACTOR_PWD", "SINGLE_FACTOR_CERT","ORDERING") VALUES (NEXTVAL(''SEQ_IAM_IDENTITY_SERVICES''),''JOC'',''JOC-RESCUE'',0,0,''SINGLE'',1,0,0)';
  

Desired Behavior

• The right SQL statement is

  EXECUTE
  'INSERT INTO IAM_IDENTITY_SERVICES("ID","IDENTITY_SERVICE_TYPE", "IDENTITY_SERVICE_NAME","REQUIRED","DISABLED", "AUTHENTICATION_SCHEME","SECOND_FACTOR", "ORDERING") VALUES (NEXTVAL(''SEQ_IAM_IDENTITY_SERVICES''),''JOC'',''JOC-RESCUE'',0,0,''SINGLE'',0,0)';
  

• Similar changes are applied to SQL rescue scripts for all DBMS.

Workaround

• SQL rescue scripts for all DBMS are attached this issue.
  • Download the attached db.tar.gz or db.zip file:
    • extract to the JOC Cockpit home directory, for example:

    • tar xzf db.tar.gz -C /opt/sos-berlin.com/js7/joc

• After extraction the downloaded scripts should be available from the following location:

  <joc-home>/db/<dbms>/identity_service_rescue.sql
  

   

• • With <joc-home> being the JOC Cockpit's home directory and <dbms> being one of h2, mssql, mysql, oracle, pgsql.
• To reset Identity Services after access to JOC Cockpit was lost users can run the script

  <joc-home>/install/joc_install_tables.sh --rescue