You can put several user accounts together to form a user group, which you can store on the local database or on a RADIUS, LDAP, or SecurID server. When you reference an authentication user group and an external authentication server in a policy, the traffic matching the policy provokes an authentication check.
In this example, the access profile called prof_1 is configured for external authentication. Two RADIUS servers and one LDAP server are configured in the access profile. However, the order of authentication specifies RADIUS server only, so if the RADIUS server authentication fails, then the firewall user fails to authenticate. The local database is not accessed.
![]() |
Note: If the firewall clients are authenticated by the RADIUS server, then the group-membership VSA returned by the RADIUS server should contain alpha, beta, or gamma client-groups in the RADIUS server configuration or in the access profile, prof_1. Access profiles store usernames and passwords of users or point to external authentication servers where such information is stored. |
Before You Begin |
|---|
For background information, read Firewall User Authentication Overview. |
To configure a server for external authentication, use either J-Web or the CLI configuration editor.
This topic covers:
To specify the RADIUS server for external authentication order using the J-Web configuration editor:
The Configuration page appears.
To configure firewall user (ClientsA-E) and assign firewall users (ClientA and ClientB) to client groups alpha, beta, and gamma:
To configure client groups in the session options:
The Configuration page appears.
To configure the IP address for the LDAP server and LDAP server options:
To configure the IP addresses for the two RADIUS servers:
To configure the device for external authentication using a RADIUS server follow these steps:
- user@host# set access profile prof_1 client
clientA client-group alpha
- user@host# set access profile prof_1 client
clientA client-group beta
- user@host# set access profile prof_1 client
clientA client-group gamma
- user@host# set access profile prof_1 client
clientA firewall-user password pwd1
- user@host# set access profile prof_1 client
clientB client-group alpha
- user@host# set access profile prof_1 client
clientB client-group beta
- user@host# set access profile prof_1 client
clientB firewall-user password pwd3
- user@host# set access profile prof_1 client
clientC firewall-user password pwd4
- user@host# set access profile prof_1 client
clientD firewall-user password pwd5
- user@host# set access profile prof_1 client
clientE firewall-user password pwd2
- user@host# set access profile prof_1 session-options
client-group u1
- user@host# set access profile prof_1 session-options
client-group alpha
- user@host# set access profile prof_1 session-options
client-group gamma
- user@host# set access profile prof_1 session-options
client-idle-timeout 255
- user@host# set access profile prof_1 session-options
client-session-timeout 4
- user@host# set access profile prof_1 ldap-options
base-distinguished-name
- CN=Users,DC=screenos,DC=spg,DC=juniper,DC=net
- user@host# set access profile prof_1 ldap-options
search search-filter sAMAccountName=
- user@host# set access profile prof_1 ldap-options
search admin-search distinguished-name
- cn=administrator,cn=users,dc=screenos,dc=spg,dc=juniper,dc=net
- user@host# set access profile prof_1 ldap-options
search admin-search password pwd10
- cn=administrator,cn=users,dc=screenos,dc=spg,dc=juniper,dc=net
- user@host# set access profile prof_1 ldap-server
3.3.3.3