Jar signing: issue with adsign.txt and admin not creating proper jarlist.txt

[iqbaljawaid138]

Hi,
I have EBS 12.2.8.
ISSUE -1 After generating the .csr for code signing I lost the adsign.txt. how can I regenerate adsign.txt. And if regenerated by reinitializing then will my previously acquired certificates be still be compatible with regenerated key.

ISSUE -2 Used adadmin to FORCE sign the jar files, and compared the jarlist.txt and jarlist.bak (which is a backup of pre-sign jarlist.txt), found that the new jarlist.txt has only one line refering to CUSTOMSALL.jar only.

Whereas jarlist.bak has refernece to all the .jar files.
Kindly help , What has gone wrong.

Regards,
Mohammad Jawaid  

[ErmanArslansOracleBlog]

ISSUE 1 . You lost the CSR file I guess.
So now you have the certificates (signed) and have to import them. You should be able to do that. Itseems adsign.txt , which is used to pass arguments to the JRI during file signing , is lost.. You need adkeystore.dat and adsign.txt otherwise adadmin/adpatch will fail during jar files generation.. Restore it from backup if you can other.. Other than that -> Generating your keypair will create new adkeystore.dat and adsign.txt files.

ISSUE 2-> Probably adadmin thinks that the other files doesn't need to be signed. What is the story of this environment? Is this a second try o something? Please give me the details, check the adadmin logs (once executed with force option) and try to see the reason for that..