How to resolve AutoUpdate issues due to missing Juniper Public Key.
By default, on the JSA Console (7.3 releases) there are two gpg keys present which we can validate with the following command:
gpg --list-keys
Output:
/root/.gnupg/pubring.gpg ------------------------ pub 1024D/69865E78 2009-04-21 uid Autoupdate Generation (AUGen) sub 2048g/4D4080FD 2009-04-21 pub 1024D/E6FF3F75 2011-06-20 uid Juniper Networks STRM (STRM Auto-Update) <[email protected]> sub 2048g/02328E16 2011-06-20
Note: Key numbers are Highlighted in the output above.
If any or both the Key(s) are missing, then the AutoUpdate may show the following error message:
[ERROR] Could not verify the authenticity of /store/autoupdates/patches/patches.manifest.xml.
If any or both of them are missing, then download the relevant key from the following link:
JSA_AU_Keys (A zip file: JSA_AU_Keys.zip will be downloaded which contains: JSA-AU_E6FF3F75.key & JSA-AU_69865E78.key )
Transfer the JSA-AU>##.key file to your JSA Console server.
Go to the specific directory where we have transferred the file and run the import commands as per your requirement (after validating which key is missing)
gpg --import JSA-AU_E6FF3F75.key
gpg --import JSA-AU_69865E78.key
Post which validates the public key list:
gpg --list-keys /root/.gnupg/pubring.gpg
------------------------ pub 1024D/E6FF3F75 2011-06-20 uid Juniper Networks STRM (STRM Auto-Update) <[email protected]> sub 2048g/02328E16 2011-06-20 pub 1024D/69865E78 2009-04-21 uid Autoupdate Generation (AUGen) sub 2048g/4D4080FD 2009-04-21
Now we can again trigger the AutoUpdate job from the GUI.