JSC was tested with multiple clients and in all the scenarios JSC was left with connection enabled.

Within 24 hours, it was noticed that the JSC connection froze.

Often, the client workstation will need a reboot in order to restore a new VPN connection. Issue is observed when the SAML version of the JSC had been installed in the client machines.

Clients/Hosts can no longer access JSC and need to restart the machines altogether.

JSC tab and logging prompt in client machine is frozen

This issue happens when the SAML version of the Juniper Secure Connect client program is installed in the hosts/client and the SRX is non-SAML approved, such as branch SRX devices. Issue is observed in vSRX as well when the SAML supported JSC client had been installed.

In order to fix the issue it is necessary to install a non-SAML version onto the clients/hosts:

Non-SAML version for Windows:

25.4.13 

23.4.13

After installing either the 25.4.13 (non-SAML) or 23.4.13 (non-SAML) on the clients, the issue no longer happened.

Please refer to the KB below for the SAML supported JSC clients and the SRX versions.

KB75995 [juniper.net] - SRX] [JSC] Juniper Secure Connect - SAML Authentication

2025-10-24 : Article Created

2026-02-16: Description and the resolution modified. Making KB public