adop Patch 36271505 and adadmin failing at generate jar files failing on EBS 12.2.12

adop Patch 36271505 failed with error:

ERROR: JarSigner subcommand exited with status 1

Also tried adadmin --> generate jar files with Force "Yes" option but still failing with same error:

++++++++++++++++++++

[UNEXPECTED]Apply phase has failed.
 [PROCEDURE] [START 2024/06/18 14:58:19] Updating adop session status
    About to Generate fndlist.jar : Tue Jun 18 2024 14:58:18

    [STATEMENT] SQL statement : "  update ad_adop_sessions

    Done Generating fndlist.jar : Tue Jun 18 2024 14:58:18

    About to Sign fndlist.jar : Tue Jun 18 2024 14:58:18
ERROR: JarSigner subcommand exited with status 1
JarSigner standard output:
jarsigner error: java.lang.RuntimeException: keystore load: Keystore was tampered with, or password was incorrect
JarSigner error output:
Enter Passphrase for keystore:
  Done Analyzing fndlist.jar : Tue Jun 18 2024 14:58:19

ERROR: The following jars failed to get generated properly.
----------------------------------------------------------------------------
/Apps/EBS122/fs2/EBSapps/comn/java/classes/oracle/apps/fnd/jar/fndctx.jar
/Apps/EBS122/fs2/EBSapps/comn/java/classes/oracle/apps/fnd/jar/wfmon.jar
/Apps/EBS122/fs2/EBSapps/comn/java/classes/oracle/apps/fnd/jar/wfapi.jar

++++++++++++++++++++++++

Conclusion:

There are several reasons for this error and in my case, I found issue with Jar signing. (ref Doc ID 1591073.1)

Followed below steps and issues fixed.

Fix:

Step 1) adjkey -initialize 

NOTE: 

 a)You can mention Alias name "mycert" similar to soruce instance from where you are     planning to copy adkeystore.dat/adsign.txt/cacerts files .

 b)You can run "adjkey -list" to find alias name.

 c)Don't worry about below input parameters brecause those values will overwritten       from the files you are copying from source

 d) Ignore below output warnings of command "adjkey -initialize"

Warning:

The JKS keystore uses a proprietary format. It is recommended to migrate to PKCS12 which is an industry standard format using "keytool -importkeystore -srckeystore /Apps/EBS122/fs_ne/EBSapps/appl/ad/admin/adkeystore.dat  -destkeystore /Apps/EBS122/fs_ne/EBSapps/appl/ad/admin/adkeystore.dat -deststoretype pkcs12".

  IMPORTANT: If you have multiple web servers, you must copy

  files to each of the remaining web servers on your site.

  See the documentation reference for more information.

step 2) Change keystore passwords using below steps (if possible set similar password as source and later you can change)

2.a) Change your keystore (store) password

Run the following command substituting the values in bold as applicable:

$ adjkey -storepasswd   

  Enter the APPS username: <appsusername>

  Enter the APPS password: <appspassword>

  Enter the new keystore password: <new store passwd>

  

2.b) Change your key password

Run the following command substituting the values in bold as applicable:

$ adjkey -keypasswd   

  Enter the APPS username: <appsusername>

  Enter the APPS password: <appspassword>

  Enter the new key password: <new key passwd>

  

If required you can identify and change the keystore passwords by running the commands below.

Identify Your Keystore Passwords

To identify the existing keystore and key passwords run the following SQL script connected as the APPS user:

SQL> set serveroutput on

declare

spass varchar2(30);

kpass varchar2(30);

begin

ad_jar.get_jripasswords(spass, kpass);

dbms_output.put_line(spass);

dbms_output.put_line(kpass);

end;

/

This will output the passwords in the following order:

store password (spass)

key password (kpass)

  

Step 3) Copy Files to the Target Environment.

 

EBS 12.2.x Users

$ cp $NE_BASE/EBSapps/appl/ad/admin/adsign.txt $NE_BASE/EBSapps/appl/ad/admin/adsign.txt.presign

$ cp $NE_BASE/EBSapps/appl/ad/admin/adkeystore.dat $NE_BASE/EBSapps/appl/ad/admin/adkeystore.presign

Copy the files taken from your source environment to the directory listed above on your target environment as appropriate to your Oracle E-Business Suite release.

NOTE: In my case, I copied files adsign.txt/adkeystore.dat/cacerts from working environment:

Step 4) Back up cacerts File on 'Target' Environment

Back up the existing cacerts file on your target environment as applicable to your Oracle E-Business Suite release.

Oracle E-Business Suite Release 12 Users

$ cp $OA_JRE_TOP/lib/security/cacerts $OA_JRE_TOP/lib/security/cacerts.presign

ls -tlr $OA_JRE_TOP/lib/security/cacerts

keytool -list -keystore cacerts

cd $OA_JRE_TOP/lib/security

mv cacerts cacerts_source_backup

cp <any working instance)/cacerts $OA_JRE_TOP/lib/security/

chmod a-w cacerts

Step 5) Regenerate the jar Files

Regenerate the jar files on the Target instance using the 'force' option through adadmin, see Section 5: Regenerate the jar Files.