Managing the Internal Database
You can create entries in the internal database to authenticate clients. The internal database contains a list of clients, along with the password and default role for each client. When you configure the internal database as an authentication server, client information is checked in incoming authentication requests against the internal database.
Configuring the Internal Database
Mobility Master uses the internal database for authentication by default. You can choose to use the internal database in a managed device by entering the CLI Command-Line Interface. A console interface with a command line shell that allows users to execute text input as commands and convert these commands to appropriate functions. command . If you use the internal database in a managed device, you need to add clients on the managed device.
The following CLI Command-Line Interface. A console interface with a command line shell that allows users to execute text input as commands and convert these commands to appropriate functions. command configures the internal database:
(host) [mynode] #local-userdb add {generate-username|username <name>}{
generate-password|password <password>}
Managing Internal Database Files
Mobility Master allows you to import and export user information tables to and from the internal database. These files should not be edited once they are exported. Mobility Master only supports the importing of database files that were created during the export process. Note that importing a file into the internal database overwrites and removes all existing entries.
The following CLI Command-Line Interface. A console interface with a command line shell that allows users to execute text input as commands and convert these commands to appropriate functions. commands configure the import and export of internal database files:
(host) [mynode] #local-userdb export <filename>
(host) [mynode] #local-userdb import <filename>
