Junos Pulse User Agent for iPhone continuous change !

[NicolasBedard_]

Can somebody at Juniper explain me why the user Agent from the Junos Pulse application is changing at every new version released on the App Store !!

we use this in the SA to prevent non-iOS user to connect to our SA, but so far at each version they changed the User Agent and it's resulting in people unable to connect to the VPN with their mobile devices.

In the previous version there was 2 different agent:

JunosPulseiPhone

JunosPulseiPad

Now it's:

JunosPulse(Version-3.2.0.20175)iPad/iPhone

JunosPulse(Version-3.2.0.20175)iPhone

The newest issue is now that they have included the version in the UserAgent, so in the SA section fro Browser restriction the workaround I found was to include the following:

*JunosPulse(Version-*)iPad/iPhone*

*JunosPulse(Version-*)iPhone*

I just hope the Junos Pulse developper will stop messing around with the user agent and start having a fixed way of identifying the Apps to the SA appliance !!

thanks

[zanyterp_]

I am sorry to hear this has caused you concerns; it has not been brought to our attention of the non-wild carded use case.

Can you work with your account team, please, to get a request in to have this made static or otherwise standardized?

[DHayes_]

We used the user-agent string as well for restricting access and had Production issues because of this change. Does anybody know if this was covered in the release notes?

[rdrombos_]

Looks like there are a couple of unexpected changes on the latest release of Pulse. This biggest is that the user agent string changed. We use this string to determine what roles to offer. After the Pulse client upgrade our check of user agent string (Roles/General/Restrictions/Browser) does not match so upgraded users are not offered a Pulse compatible role. I have to step through each Pulse role and change the acceptable user agent strings and add these new values. (5 done - 61 to go).

Looks like there is now a user license agreement that has to be accepted. Most users will figure out they need to accept to use the software.

The log in screen now includes a window pane to log on to NetMeeting. We don't use this so I'm hoping this does not cause too many user complaints/questions.

We use a single URL log in screen for many purposse and user must select a realm. The realm Pulse users have to select doesn't show up when selected, nor is it remembered in subsequent sessions. I think these are bugs that will need to be fixed. To select the correct realm the user must first select a different realm, then select the Pulse realm. This is going to cause user problems.

[jspanitz_]

While I can see the problem with the change, I also see the plus side, which is the ability to restrict users if they have an older version of Pulse, unless there is another way of doing it.

[zanyterp_]

---

@rdrombos wrote:

Looks like there are a couple of unexpected changes on the latest release of Pulse.  This biggest is that the user agent string changed.  We use this string to determine what roles to offer.  After the Pulse client upgrade our check of user agent string (Roles/General/Restrictions/Browser) does not match so upgraded users are not offered a Pulse compatible role.  I have to step through each Pulse role and change the acceptable user agent strings and add these new values. (5 done - 61 to go).

Looks like there is now a user license agreement that has to be accepted.  Most users will figure out they need to accept to use the software.

We use a single URL log in screen for many purposse and user must select a realm.  The realm Pulse users have to select doesn't show up when selected, nor is it remembered in subsequent sessions.  I think these are bugs that will need to be fixed.  To select the correct realm the user must first select a different realm, then select the Pulse realm.  This is going to cause user problems.

---

The EULA is needed for each version; it has been in place since the first release.

Please open a case for tracking the failure with the realm not showing; it should be there without needing to modify the selection. Are you allowing the realm to be saved?

[zanyterp_]

You are correct, it is not possible to restrict based on version, if desired, until now.