Forcing Execution Of Commands - Lantronix SCS Reference Manual

Security
Local authentication can execute and restrict user commands.
CHAP may be used for authentication.
Disadvantages include:
The SCS cannot share its databases with other servers.
The SCS cannot share existing databases.
The local database is limited by the size of the server's NVR.
11.4.1.1 Changing the Precedence
By default, the precedence for the local database is set to 1. To change the precedence number, use the Set/
Define Authentication Local command.
Local>> DEFINE AUTHENTICATION LOCAL PRECEDENCE 3
11.4.1.2 Adding Username/Password Pairs
To add a username/password pair to the local database, use the Set/Define Authentication Local
command.
Figure 11-20: Adding User and Password to Local Database
Local>> DEFINE AUTHENTICATION USER "elmo" PASSWORD "badger"
All passwords are case sensitive. All usernames are case insensitive.
Note:

11.4.1.3 Forcing Execution of Commands

A command or series of commands may be associated with a particular username; the commands will be
run when the user is successfully authenticated. For example, when user elmo logs into the SCS, he will be
automatically telnetted to host 192.0.1.67 and logged out of the SCS.
Local>> DEFINE AUTHENTICATION USER "elmo" COMMAND "telnet 192.0.1.67; logout"
Commands must be enclosed in quotes. If a series of commands is specified, they must be separated by
semicolons.
11.4.1.4 Permitting Users to Change Their Passwords
By default, users are not permitted to change their passwords. To enable a user to change his or her
password, use the Set/Define Authentication User Alter command.
Local>> DEFINE AUTHENTICATION USER "elmo" ALTER ENABLED
Figure 11-19: Specifying the Precedence
Figure 11-21: Forcing Commands
Figure 11-22: Permitting User to Change Passwords
11-10
Database Configuration