BlackBerry® PlayBook™

[tigerpaws]

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. 

[g4qber]

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

[TroyTempest]

I don't see Dolphin HD in appworld. Only free dolphin.

[g4qber]

you are correct

I was thinking about the ipad version

Please use Dolphin Free for Playbook

[tigerpaws]

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 2.1.0.1088, and this doesn't help. On the iPad this works with Safari, but not the ipad browser. 

[cr8tive_leo]

Just a thought, Myself and a few co workers also ave Playbooks, we had huge issues getting onto internal sites when using 2.0 os, we all upgraded to the latest one, and it solved all our problems.
You didn't mention the version of os you're running, this may help, unless you are already on it, then... no clue.

[piece1991]

i think i have the same problem.

have yours get solved?