Beginning with the iOS 3.2 client, the user-agent string has changed. If user-agent restrictions are configured on the realm or role, certain iOS clients might have difficulties with logging in.
- The IVE administrator has configured user-agent restrictions on the realm or role to provide access, which is based on the client being used.
- The restriction was in the form of JunosPulse iPad or JunosPulse iPhone.
- After upgrading the client, users are prevented from connecting successfully.
Starting with Pulse 3.2 on iOS, the client software version is included in the user-agent string.
iOS 3.2.2 user-agent strings:
JunosPulseiPhone Mozilla/5.0 (iPhone; CPU iPhone OS 5_1_1 like Mac OS X) AppleWebKit/534.46 (KHTML, like Gecko) Mobile/9B206 JunosPulse(Version-188.8.131.5249)iPhone
JunosPulseiPad/iPhone Mozilla/5.0 (iPad; U; CPU OS 4_3_1 like Mac OS X; en-us) AppleWebKit/533.17.9 (KHTML, like Gecko) Mobile/8G4 JunosPulse(Version-184.108.40.20649)iPad/iPhone
iOS 3.2 user-agent string:
iOS 3.0.3 user-agent string:
When using user-agent string restrictions, be aware that the user-agent may change in the future.
When using a literal form, such as JunosPulse(Version-220.127.116.1175)iPad/iPhone, you are permitting only clients that match the user-agent string to login. If possible, it is recommended to use wildcards in the restrictions,
- *JunosPulse*iPad* should be used to recognize iPad.
- *JunosPulse*iPhone* should be used to recognize iPhone.
Note: iPad match should be listed prior to iPhone.
- *JunosPulse*Android* to recognize Android.
Note: This article will be updated as and when changes are made to the user-agent string. The user agent strings for different browsers can be found via the following link:
Go to the above link by using different browsers to get the correct user-agent string on iOS clients and other client machines.