02-22-2012 06:13 AM - edited 02-22-2012 06:30 AM
I'm having issues with the Junos Pulse Client for Android running on several test devices running 2.2 and 2.3.5 Android. These are not samsung devices so I'm not expecting Layer 3 access.
If I configure the Junos Pulse client to connect using https://server.domain.com it will connect to the gateway, log in with username/password and it then displays the intranet button as expected. After hitting this it succesfully displays the expected Web Bookmarks list. However when a bookmark is selected we are prompted to login again but in the address bar the server is displayed as https://<IP Address>/.... It appears to be this change to IP instead of server.domain.com that is causing the issue, because if the pulse client is configured to use IP it all works.
Can anybody give any reason for this change from name to IP? I've tried changing the signin policies to be server.domain.com/ instead of the default */ but this made no difference.
IVE Gateway 7.1R5 (SA2500)
Junos Pulse 184.108.40.20659
Android 2.2 and 2.3 devices
Solved! Go to Solution.
02-23-2012 01:21 PM
I believe you are running into an issue that will be resolved in Junos Pulse 3.0.4 in a few weeks. I can update the post when it's officially released in the market and see if this resolves the issue.
03-07-2012 07:12 PM
We have released Pulse 220.127.116.1179 in Google Android market. We are yet to release the correpsonding Pulse version specifically for Samsung devices which supports L3 VPN.
I've tested with 18.104.22.16879 and I see that the reported behavior got fixed. You may wish to test it and use it....
03-08-2012 05:22 AM
Hi, thanks for the update. It is now working but seems to be extermely slow at re-writing even basic websites.
I've also been testing certificate based auth which works ok on Androids (after getting the certificates installed) but wondered if it is possible to do Certificate and AD auth chained? May post this question to a new thread.