You can add local users to the internal database on the network security appliance from the Device > Users > Local Users & Groups page.
To create a user for an SSL VPN client, refer to SonicOS 8 SSL VPN Administration Guide.
To add local users to the database
To invalidate compromised passwords, from the Restrict access until password is changed drop-down menu, select the level of restriction.
This option is supported in SonicOS 8.2 and higher versions.
This restriction applies to web login, login from a VPN client and CLI login via SSH. It does not restrict administrator login on the console, or user’s login via SSO. It can only be set for a local non-domain user accounts that have configured passwords.
Block remote access: The user is allowed to log in only from the trusted locations. A user can restore remote access by resetting password but only if they can access a secure internal location. Otherwise, the user must contact a firewall administrator.
The trusted locations include the LAN zone, the MGMT zone, and any other zones with security type 'Trusted', and remote locations connected through a site-to-site VPN tunnel including NSM.
Block all but console access: The user is not allowed to login from any locations apart from the admins on the console port. To restore remote access, a user must contact a firewall administrator.
Block remote except SonicWall Unified Management / NSM On-premise: The user is not allowed to login from any locations except SonicWall Unified Management/NSM On-premise. To restore remote access, a user must contact a firewall administrator.
Block all but console and SonicWall Unified Management / NSM On-premise: The user is not allowed to login from any locations apart from the admins on the console port and SonicWall Unified Management/NSM On-premise. To restore remote access, a user must contact a firewall administrator.
From the One-time password method list, select the method to require SSL VPN users to submit a system-generated password for two-factor authentication:
When a Local User does not have a one-time password enabled, while a group it belongs to does, ensure the user’s email address is configured, otherwise this user cannot login.
To avoid another password change request for this user, this option applies only to the first login.
TOTP – Users receive a dynamic, time-sensitive verification code generated by an authenticator application on their mobile device or computer after entering their username and password. To use this method, users must install a supported TOTP client application, such as Google Authenticator, Microsoft Authenticator, or Duo Mobile, and enroll by scanning the registration QR code or entering the secret key.
Unbind TOTP key — Click this option to disassociate the user's current authenticator app profile from their account. When unbound, the user's existing TOTP secret key is cleared, prompting them to complete the initial QR code registration workflow the next time they log in (for example, if they lost or replaced their mobile device).
In Account Lifetime, select Never expires to make the account permanently. Or select Minutes, Hours, or Days to specify a lifetime after which the user account will either be deleted or disabled.