Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?


profile (Juniper Secure Connect)


Hierarchy Level


Configure remote user connection profiles for the Juniper Secure Connect clients.

The remote access profiles allow you to deploy connection settings for the remote users by pushing the configuration file on the client devices. You can create multiple profiles and set one of the profiles as the default profile.


Starting in Junos OS Release 23.1R1, we’ve hidden the default-profile option at the [edit security remote-access] hierarchy level. In releases before Junos OS Release 23.1R1, you use this option to specify one of the remote-access profiles as the default profile in Juniper Secure Connect. But with changes to the format of remote-access profile names, we no longer require the default-profile option.

We’ve deprecated default-profile option—rather than immediately removing it—to provide backward compatibility and a chance to make your existing configuration conform to the changed configuration. You’ll receive a warning message if you continue to use the default-profile option in your configuration. However existing deployments are not affected if you modify the current configuration. See default-profile (Juniper Secure Connect).

Each remote access profile includes a realm-name mapping to an URL either in FQDN/RealmName or FQDN format, authentication settings, VPN settings, and client configurations. You can create different remote access profiles for different names or functions.

Example—You can create a configuration profile for the engineering department, and another for the human resource department. You name the profile for engineering department and human resource department as and respectively.

When a Juniper Secure connect remote user selects a connection profile such as, the SRX Series Firewall receives the configuration request and selects a remote-access profile with same name —that is— for pushing the configuration on client device.



Set realm-name as remote-access profile name. This is the profile identifier in FQDN/RealmName format.

Examples:, if FQDN is and Realm name is hr., if FQDN is and Realm name is engineering., if FQDN is and Realm name is empty.

Specify an IP address if you do not have an FQDN ( or


Select the access profile for authentication and accounting for clients.


Select the client configuration object.


Select pre-logon compliance rule object name.


Text description of the remote access profile.


Select the IPsec VPN policy object used for IKE and IPsec proposals.

Required Privilege Level


Release Information

Statement introduced in Junos OS Release 20.3R1.

Compliance option introduced in Junos OS Release 23.1R1.

Realms format changed to FQDN/RealmName or FQDN in Junos OS Release 23.1R1.