12-16-2011 01:15 AM
We have a number of internal company sites that are protected by https with a private SSL certificate signed by our CA. The only way to access these sites is to have a certificate we made. On the playbook, I carefully followed KB#26515 and installed my root CA public certificate in the trusted certificate store, and my own certificate in the personal certificate store, pretty much the same way it is set up on my computers in any browser. However, when i try to access any of our sites, I get "Unknown netowrk error 3RFINA" on the playbook. There is only 1 personal certificate, so the browser has to send that when it is requested by the server.On windows, using IE, I get asked to select a certificate, even if there is only one. The playbook doesn't ask, so I presume it's sending the right one. Can anyone helpme to understand what this error means and what I can do to fix it?
We have several people with playbooks all with the same need to get to our internal sites.
Thanks in advance.
09-22-2012 09:08 PM - edited 09-23-2012 07:40 PM
use Dolphin <<error - HD>> browser to authenticate
then can use default playbook browser
in Perth West Aust, Good Guys certificate is 2010 & playbook baulks at this.
iPhone, iPad & Samsung Galaxy Tab seem to be OK with this.
hope this works for you
10-29-2012 09:44 PM
I can't get the dolphin browser to do https either. Using the debug log in the web server, it is clear that none of the browsers on the pb honor the server's request for my private certificate, even though it is properly installed in the certificate manager. I have just updated to the latest version of the OS 18.104.22.1688, and this doesn't help. On the iPad this works with Safari, but not the ipad browser.
10-30-2012 11:53 AM
07-17-2013 10:18 AM
I guess the problem is invalid certificate in web authlogin page.
Even when I add a excepetion, I still geting this same error 3RFINA.
I remember when I had Android 1.6 I receive similar error, but when upgraded to 2.1 the errors was gone and I was able to authenticate in wifi connection here in that government build.
Now, when I came to BB Z10, I a kind of disapointed to get same error. I now its concern by security and the guilty in that history probably is IT who admin this network for using a invalid certificate (the validation date appears in browser is a kind of funny... says its valid from 2027 to 2039)