Explanation:
VPN-1 & FireWall-1 Password
The simplest authentication scheme provided on VPN-1/FireWall-1 is the VPN-1 & FireWall-1 Password scheme. This scheme relies on a unique username and password to authenticate users, which are stored in the users database in a user object that represents each user. The users database is stored on the management server and is installed to each enforcement module by the management server. A username can be up to 100 characters in length and can use any alphanumeric character. The password must be between four to eight characters. Figure below shows how the VPN-1 & FireWall-1 Password scheme works. In Figure below, the master VPN- 1/FireWall-1 users database resides on the management server. Each enforcement module also maintains a local copy of the users database, which is installed from the management server master database. The user authentication database allows each enforcement module to authenticate users locally, without having to pass the authentication request back to the master users database on the management server. This increases the performance and responsiveness of the enforcement module when authenticating.

The simplest authentication scheme provided on VPN-1/FireWall-1 is the VPN-1 & FireWall-1 Password scheme. This scheme relies on a unique username and password to authenticate users, which are stored in the users database in a user object that represents each user. The users database is stored on the management server and is installed to each enforcement module by the management server. A username can be up to 100 characters in length and can use any alphanumeric character. The password must be between four to eight characters. Figure below shows how the VPN-1 & FireWall-1 Password scheme works. In Figure below, the master VPN-1/FireWall-1 users database resides on the management server. Each enforcement module also maintains a local copy of the users database, which is installed from the management server master database. The user authentication database allows each enforcement module to authenticate users locally, without having to pass the authentication request back to the master users database on the management server. This increases the performance and responsiveness of the enforcement module when authenticating.

---