Home > Blackberry Error > Blackberry Error Initializing Server Socket Factory Ssl Context

Blackberry Error Initializing Server Socket Factory Ssl Context

Is it possible, then, that he uses that for a default if javax.net.ssl.trustStorePassword is not set? Join & Ask a Question Need Help in Real-Time? The documentation does appear to be a bit lacking in the area of JSSE and RMI interaction. The only reason we ever used the Sun JSSE was that when we started this, it was the only game in town. navigate to this website

I know they were doing this successfully because if the server's certificate was not in there, or it was expired, they wouldn't talk to him. Model: Z10 OS: 10.0.0 PIN: NUKE(PAP) Carrier: Singtel Posts: 1,504 Post Thanks: 6 Thanked 9 Times in 9 Posts RIM has since created a KB article:- Article Title: "Keystore was tampered Why does IBM? The documentation does appear to be a bit lacking in the area of JSSE and RMI interaction.

Log in to reply. I'm back, and yes, it's been a year. SystemAdmin 110000D4XK ‏2003-04-09T08:31:30Z I've just had another look at the code and and I don't think the trustStorePassword is relivent. This is the Windows System process and through a considerable amount of googling I was unable to identify which roles was causing System to listen on port 443.

More... Send to Email Address Your Name Your Email Address Cancel Post was not sent - check your email addresses! Email check failed, please try again Sorry, your blog cannot share posts by email. %d bloggers like this: SYS-Admin exitus solutio About Me Tools Index Posted by: David | July 31, SystemAdmin 110000D4XK 2262 Posts Re: JSSE SSLContext IllegalAccessException ‏2003-03-31T14:40:46Z This is the accepted answer.

Dims? I just changed the password on cacerts to the same as on the server's keystore, and set the keyStorePassword property as I'd always done, and then he seemed to to succeed SystemAdmin 110000D4XK ‏2003-04-08T16:18:28Z Well, one of the points of using Java was that there weren't supposed to be any differences in implementation between vendors that would make the products not work I had to fix it ASAP so I decided to reinstall BES express.

Buy my KnottyRope App hereBES 12 and BES 5.0.4 with Exchange 2010 and SQL 2012 Hyper V Report Inappropriate Content Message 3 of 7 (9,226 Views) 0 Likes tonty1970 New Contributor thanks, Vicky Log in to reply. So now we're back to the problem of making RMI over SSL work under both the IBM and Sun JSSE 1.4 implementations, and we have solved our problem. SystemAdmin 110000D4XK ‏2003-03-28T17:29:58Z Not sure, I've passed the question on to the developer who works on the SSL code.

This is the accepted answer. Did he read it before? This is the accepted answer. Automated exception search integrated into your IDE Test Samebug Integration for IntelliJ IDEA Root Cause Analysis java.io.IOException Error initializing server socket factory SSL context: null   I Depend On:     jboss.messaging:service=SocketBuilder,type=SSL

We requested an instance of KeyManagerFactory for algorithm "SunX509". http://onlinetvsoftware.net/blackberry-error/blackberry-error-503.php None of these were required before in our 1.3 code, but they seemed reasonable enough: code permission java.util.PropertyPermission "javax.net.ssl.trustStore", "read"; permission java.util.PropertyPermission "java.home", "read"; permission java.io.FilePermission "/usr/java14/jre/-", "read"; permission java.util.PropertyPermission "javax.net.ssl.trustStoreType", Leave a Reply Cancel reply Enter your comment here... I am having a different problem with the IBM JRE: I can't import a PKCS7 certificate chain into the keystore using keytool.

Apparently yes. I don't think that the password is necessary to check the cacerts file for trusted certificates. Not sure, I've passed the question on to the developer who works on the SSL code. my review here SystemAdmin 110000D4XK ‏2003-04-08T17:35:35Z So, that answers one of my questions - the client now has to know the password to the trusted store?

How did you tell you application which passwords to use? Stack Overflow | user3601554 | 2 years ago 0 mark Jboss 5.2 Cluster JNP lookup issue Stack Overflow | 2 years ago | user3601554 java.io.IOException: Error initializing socket factory SSL context: any other ideas out there?

I don't know why, and it really doesn't make sense, but we didn't tell our clients ANY password, and yet they could open the system trusted store (cacerts) and check the

We show this process by using the Exchange Admin Center. Click here to Backup the data on your BlackBerry Device! Some how this can be looked by the services running on the BES machine. What differences between IBM's and Sun's implementation am I hitting and what can I do about it? >How did you tell you application which passwords to use?

The code which was failing with the keystore error was from my client socket factory (which I believe rmi uses): code public class HPSSClientSocketFactory implements RMIClientSocketFactory, Serializable { public Socket createSocket( An additional piece of evidence: once I got the server started, I tried the client. So far as I can tell, things seem to be pretty much the same with the exception of pointing to the new packages. get redirected here No trackbacks yet.

We did not have javax.net.ssl.keyStore set, and the JSSE Reference Guide says there is no default for the keystore. Topic Forum Directory >‎ dW >‎ Java >‎ Forum: Java security >‎ Topic: JSSE SSLContext IllegalAccessException 17 replies Latest Post - ‏2004-10-20T19:38:57Z by SystemAdmin Display:ConversationsBy Date 1-18 of 18 Previous Next The server used this to open the keystore which contained his private key. How come?

Good luck with your PKCS7 certificate. I have two keystores. This is the accepted answer. Please edit your Personal Profile with your DEVICE TYPE, DEVICE OS and Carrier Re: Cannot connect to BAS after upgrade to 5.0.3 Options Mark as New Bookmark Subscribe Subscribe to RSS