Customer is attempting to configure Juniper Secure Connect and has defined multiple access profiles, each with their own access credentials.

E.g.

set access profile JSC-ACCESS-PROFILE-1 authentication-order password

set access profile JSC-ACCESS-PROFILE-1 client test1 firewall-user password Juniper123

set access profile JSC-ACCESS-PROFILE-1 address-assignment pool JSC-POOL-1

set access profile JSC-ACCESS-PROFILE-2 authentication-order password

set access profile JSC-ACCESS-PROFILE-2 client test2 firewall-user password Juniper123

set access profile JSC-ACCESS-PROFILE-2 address-assignment pool JSC-POOL-2

They want to take advantage of defining multiple dhcp pools so that each access profile (with its set of users) can take advantage of being assigned an IP from that pool. They have a single IKE gateway to want to assign both profiles into:

E.g.

set security ike gateway JSC-IKE-GATEWAY-1 ike-policy JSC-IKE-POLICY

set security ike gateway JSC-IKE-GATEWAY-1 dynamic user-at-hostname "[email protected]"

set security ike gateway JSC-IKE-GATEWAY-1 dynamic ike-user-type shared-ike-id

set security ike gateway JSC-IKE-GATEWAY-1 external-interface ge-0/0/4

set security ike gateway JSC-IKE-GATEWAY-1 local-address 192.168.1.1

set security ike gateway JSC-IKE-GATEWAY-1 aaa access-profile JSC-ACCESS-PROFILE-1

set security ike gateway JSC-IKE-GATEWAY-1 aaa access-profile JSC-ACCESS-PROFILE-2

set security ike gateway JSC-IKE-GATEWAY-1 version v1-only

Upon committing the aforementioned configuration, a commit error can be seen announcing that multiple profiles exceeds its limit of 1:

root@SRX# commit check

[edit security ike gateway JSC-IKE-GATEWAY-1 aaa]

 'access-profile'

 number of elements exceeds limit of 1

error: configuration check-out failed: (number of elements exceeds limit)

This is expected behavior as only one access profile per IKE gateway is supported.