Unsolved
This post is more than 5 years old
2 Intern
•
615 Posts
0
3428
January 22nd, 2018 08:00
OME 2.3 Catalog signature verification failed
Seeing a failure for catalog import in OME.
OME 2.3.0.1721
Import Dell EMC Version Control Catalog for System Update from http://downloads.dell.com/catalog/catalog.cab failed.Exception message: Catalog signature verification failed. Please enable/verify proxy settings if required.
I update the catalog using the same method I use every month of clicking Get The Latest on the System Update tab. Always has worked fine.
I am able to download the .cab file using a browser so it's not a connectivity issue.
Any ideas on how to make OME be able to get the latest catalog functionality working again?
No Events found!
Daniel My
10 Elder
•
6.2K Posts
0
January 22nd, 2018 10:00
Hello
I just updated the catalog on OM Essentials without issue. Check the digital signature from the server you are running OME on to see if it recognizes it as OK. If you download the cab on the server and then right click>properties you should see a digital signatures tab.
Also, make sure the time and date on your server are correct.
Thanks
cameronredux
2 Intern
•
615 Posts
0
January 22nd, 2018 11:00
Thanks Daniel.
I just installed the certs when viewing them from the downloaded .cab file and now OME is able to import. Been using OME for 5 years and have never had to do that.
Francois VINCENT
1 Message
0
January 23rd, 2018 09:00
same problem for me, resolved by changing http://....catalog.cab by https://....catalog.cab
brastedd
2 Intern
•
336 Posts
0
January 23rd, 2018 11:00
Had the same problem and also resolved it by changing http to https.
jomach
9 Posts
0
January 24th, 2018 01:00
Same thing here.
jomach
9 Posts
0
January 24th, 2018 01:00
If downloading the .cab file with http, you do not have the "Digital Signatures" tab. I guess this is what happens in OME when you have the usual "http" configuration, it cannot validate the certificate because there ain't none.
In my opinion, OME should whether force you to use the "https" version or perform a protocol check that requires cert verification or not.