Code signing & OCSP

So, I'm attempting to load a signed MIDlet onto a few Nokia and Motorola phones. Unfortunately, I am encountering certificate problems. I have the proper certificate from Verisign, but I am having problems when it comes to loading the midlet onto the phone.

On the Nokia, I call up the browser and download the JAD file from our site. Then, it proceeds to attempt to install the JAR from the URL specified in the JAD. Somewhere along that process, however, the OCSP server from Verisign is contacted and this throws off the installation process as it fails. I called Verisign and they suspect that the device (first a Nokia S60 emulator) and then a Motorola Razr doesn't understand how to interpret the response from the OCSP server.

I'm wondering if this has anything to do with the certificate specifying ocsp.verisign.com in it, or is it something else. What has anyone else done to get a signed MIDlet onto a device despite signing issues?

We bought a Verisign Code Signing cert, but we're wondering if we should give it back (we're within the 30 day window) and buy another cert from elsewhere (one of those Java Verified certs, for example).

Any thoughts? Thanks in advance!

[1217 byte] By [infamouxxxa] at [2007-11-26 20:58:40]
# 1
Are you sure that OCSP server is been contacted from the device end.Kindly check whether verisign Class 3 root certificates are pre installed on the devices that you are testing your app.~Mohan
itsmohana at 2007-7-10 2:28:24 > top of Java-index,Java Mobility Forums,Java ME Technologies...
# 2

Yeah, I'm pretty sure of that thanks to watching the diagnostics window. Everything falls apart at that point. Yes, Class 3 root certs are installed on the devices.

We're regenerating our cert, so we'll see what happens then and hopefully our problem is solved.

Thanks for the reply!

infamouxxxa at 2007-7-10 2:28:24 > top of Java-index,Java Mobility Forums,Java ME Technologies...