Security Director Cloud and Juniper Security Director OnPrem 25.4.1 do not allow periods (.) in the name of a Juniper Secure Connect (JSC) VPN. This results in an invalid realm for clients because the profile name must match what is used in the JSC client.

Although VPN names with periods can be configured through the CLI,

profile <profile.name> {

 ipsec-vpn <vpn-name>;

 access-profile <accesss-profile-name>

 client-config <vpn-name>;

 options {

 multi-access;

 }

}

In SD-Cloud and JSD OnPrem 25.4.1, periods are treated as invalid characters.

• Unable to configure Remote Access Juniper Secure Connect VPNs from SDC or JSD OnPrem using periods (.).

• From Juniper Security Director OnPrem, same error message is seen:

• This was a known issue in Security Director Cloud 25.4.1 and has been resolved in the SD-Cloud 26.2.1 release, which is now in production.

• If you use Juniper Security Director On Prem, upgrade to version JSD 26.2.1 or later.

Workaround:

Rename the JSC VPN to a format that is not a fully qualified domain name. For example: 

• Instead of using the following FQDN with periods.

• use jsc-vpn