I tried, and got as far as getting past phase 1, but never got past phase 2. The built in VPN client just doesn't have the options we need for it to work with our current policy on the firewall. So I'm thinking we'd have to make a custom policy just for the PlayBooks if we wanted to use this in the future.
I don't think so as we just replaced our firewall with a SSG140 in January. I think it has to do with how you set up your policies. The PlayBook client currently just does not have the options we have our policy set up for. And the boss is real fussy about changing anything, especially when right now I'm the only one that has the PB.
I actually work for Juniper Networks and am the Technical Marketing Engineer for the Juniper SSL VPN product (Secure Access).
The Juniper Knowledge Base article was actually based on a document that I wrote and worked directly with RIM to ensure compatibility.
It is definitely possible to connect the PlayBook to Juniper SSL VPN but it is not via the SSL protocol, it is via IKEv2 (standards-based protocol). The OS requirements on the Juniper SSL VPN are version 7.0 at a minimum (supports authentication via machine certificate only), but you should be running version 7.1 ideally as it supports username/password authentication for IKEv2 (EAP-MSCHAPv2). It is NOT possible to get the PlayBook to connect to earlier versions of the IVE OS that runs on the Juniper SSL VPN appliance.
I have attached the document that I wrote. It is fairly current but is still based on the 1.x release of the OS on the PlayBook.
Sorry to hijack the tread but I'm also having issues creating a vpn from a playbook to a juniper ssg20. At the moment i just cant get past phase1 as in the log i'm being told that the packet arrived from an unrecognised gateway. Does the playbook support identity in the form of email address?