
Step 2: It could be possible that the User is attempting to connect the ISA App from a Device, different from what is presently allowed/authorized for the User in the ISA Management Console. This is enforced by the security check 'Device Binding'. In order to allow the User to connect the ISA App from this Device, please follow the instructions below:
If 'Device Binding' is toggled on at the User level:
Check whether the Device that the User is trying to connect from has already been captured in the ISA Management Console under the 'Devices' page
- If Yes, then simply edit the User profile in the 'Users' page in the ISA Management Console to allow the Device under the 'Device Binding' option so that it is treated as an Authorized Device
- If No, then temporarily Disable the 'Device Binding' toggle by editing the User Profile. Reconfigure the ISA App in order to capture the Device, and then re-enable 'Device Binding' to allow and treat this Device as Authorized
If 'Device Binding' is toggled on at the User Group level:
Check whether the Device that the User is trying to connect from is presently displayed as an Authorized Device under the User profile in the 'Users' page in the ISA Management Console
- If No, then temporarily Disable the 'Device Binding' toggle by updating the User Group. Reconfigure the ISA App in order to capture this Device, and then re-enable 'Device Binding' to allow and treat this Device as Authorized
- If Yes, then the User should be able to connect the ISA App from this Device as expected