09-11-2013 08:57 PM
Please be more specific with your question.
Have you tried it and did you see any error in specific?
Yes, it's not supported yet officially - however, if there are any report, it can be used for proactive knowledge share.
09-12-2013 11:04 AM
We have thousands of iOS users who use Pulse. We need to let them know if they can upgrade to iOS7 when it's released next week. I'm surprised Juniper doesn't release a statement about compatibilty with major software upgrades like this.
09-13-2013 09:50 AM
Pulse on iOS 7 seems to skew the initial login pages - specifically, we have noticed that the pre-logon notice, and the page to enter the login credentials seem to be stretched out and not resized correctly, based on screen resolution.
Post login, the app seems to work fine.
09-17-2013 12:10 AM
Junos Pulse Mobile 4.2.8 was released yesterday (in Sweden anyway..)
09-18-2013 11:57 AM
I did a generic test with Pulse 4.2R8 with iOS7 today. I was able to create a vpn tunnel and connect to resources through the tunnel. I will continue testing, but feel free to provide any additional feedback in this thread.
09-19-2013 02:05 PM
Juniper has identified an issue with Junos Pulse and iPhone 5s. Layer 3 VPN functionality on iOS 4.2r8 client will not work on iPhone 5s as iPhone 5s requires a 64 bit VPN plug-in. This issue does not affect iPhone 5c or any other devices running iOS7. Further updates can be found at: http://kb.juniper.net/InfoCenter/index?page=conten
10-11-2013 04:12 AM
We have an IPAD with IOS7 and the last version Junos Pulse (184.108.40.206565).
We have configured split tunneling and the corporate apps don't work. However, the same in IOS6 was right.
We have captured traffic in the internal interface and we don't see any traffic to corporate servers. Split tunneling isn't working.
Have anyone detected the same problem?
11-18-2013 08:44 PM
I have seen the same error for my users as well. JTAC has been completely clueless and it is been going on since the release of IOS7. We have replaced 20 IOS7 IPADs with IOS6 only because of this issue.
Has there been a fix for this?