ZyXEL Communications ZyWALL 310 - Page 256

Chapter 31 Web Authentication
ZyWALL Series CLI Reference Guide
256
[no] description
description
Sets the description for the specified condition. The no command clears the
description.
description: You can use alphanumeric and
()+/:=?!*#@$_%-
characters, and it can be up to 60 printable ASCII characters long.
[no] destination
{address_object |
group_name}
Sets the destination criteria for the specified condition. The no command
removes the destination criteria, making the condition effective for all
destinations.
[no] force
Forces users to log in to the Zyxel Device if the specified condition is satisfied.
The
no command means that users do not log in to the Zyxel Device.
interface
interface_name
Sets an interface on which packets for the policy must be received.
[no] schedule
schedule_name
Sets the time criteria for the specified condition. The no command removes
the time criteria, making the condition effective all the time.
[no] source
{address_object |
group_name}
Sets the source criteria for the specified condition. The no command
removes the source criteria, making the condition effective for all sources.
[no] sso
Enables single sign-on (SSO) web authentication using Microsoft Active
Directory.
When enabled, a user logs into a Windows computer using their Active
Directory (AD) username and password. The Zyxel Device then uses these AD
credentials for web authentication, through an SSO Agent server.
The
no command disables SSO web authentication.
[no] 8021x-sso
Enables single sign-on (SSO) web authentication using 8021x.
When enabled, a user logs into a WiFi network on the Zyxel Device that has
8021.x (WPA Enterprise) enabled. The Zyxel Device then uses the user’s 8021.x
username and password for web authentication.
The
no command disables SSO web authentication using 8021x.
[no] google-auth
Enables 2-factor authentication using Google Authenticator.
When enabled, a user must first authenticate on the web authentication
page using their Zyxel Device username and password (this step can be
bypassed if SSO or 8021.x-SSO is enabled), The user must then authenticate
again by entering a code from the Google Authenticator app.
To successfully authenticate, Google Authentication must already be
enabled on the user’s account and configured on their mobile device. For
details, see Section 56.4 on page 482.
show sso { agent |
port | presharekey}
Displays information about the specified condition.
Table 130 web-auth policy Sub-commands (continued)
COMMAND DESCRIPTION