Thank you for visiting the BlackBerry Support Community Forums.
BlackBerry will be closing the BlackBerry Support Community Forums Device Forums on April 1st (Developers, see below)
BlackBerry remains committed to providing excellent customer support to our customers. We are delighted to direct you to the CrackBerry Forums, a well-established and thorough support channel, for continued BlackBerry support. Please visit http://forums.crackberry.com or http://crackberry.com/ask. You can also continue to visit BlackBerry Support or the BlackBerry Knowledge Base for official support options available for your BlackBerry Smartphone.
"When we launched CrackBerry.com 10 years ago, we set out to make it a fun and useful destination where BlackBerry Smartphone owners could share their excitement and learn to unleash the full potential of their BlackBerry. A decade later, the CrackBerry community is as active and passionate as ever and I know our knowledgeable members and volunteers will be excited to welcome and assist more BlackBerry owners with their questions."
- Kevin Michaluk, Founder, CrackBerry.com
Developers, for more information about the BlackBerry Developer Community please review Join the Conversation on the BlackBerry Developer Community Forums found on Inside BlackBerry.
10-16-2009 06:12 AM
Thanks for the offer, but the server is on a private network. I'm going to try and create a 'proper' certificate and see if that makes a difference.
I'm still looking for any documentation wrt. formatting of the certificate fields and what the BB expects of them.
10-16-2009 06:43 AM
Ok, I've been hacking about and it appears there is a problem with Connector.open() and self-signed certificates.
(1) I add the certificate to the key store.
(2) I check its status by doing 'options' >> 'security options' >> 'certificates'. It has a yellow '?' symbol next to it, the details say it is explicitly trusted.
(3) I check this by opening a HTTPS page on the server using the built in browser, it works fine with no prompts.
(4) I then go back to my code, stepping through, it hangs on 'Connector.open()' with the following output:
SSL:->CH SSL:<-SH SSL:<-SC
(5) If I change the URL passed into the '.open' function so that it points to a server which has a certificate that is not self-signed, the handshake completes and Connector.open() returns.
I'm wondering whether anyone has managed to get this working with self-signed certificates...
10-16-2009 07:25 AM
HTTPS connections to servers with self-signed certs work just fine for me in JDE v4.6.1. I'm using Direct TCP/WiFi.
The log in the Output Window looks as follows:
10-16-2009 07:34 AM
Well, I managed to get it working. Drinking a celebratory coke as I type.
Unfortunately, I had to go into 'Options' >> 'Security Options' >> 'TLS' and set the values of the two fields 'Prompt for Server Trust' and 'Prompt for Domain Name' to 'No'. Either one of these being set to 'Yes' causes the handshake to hang on the 'SSL:<-SC' stage.
I'm glad you mentioned that you have it working with v4.6.1 JDE, I'm using v4.2.1 for backwards compatibility reasons and tried 4.5.0 - I think I'll build my app against 4.6.1 to see if that resolves this.
In the meantime, I think there is a bug in the JDE - that dialogue box isn't popping up.
10-19-2009 10:24 AM