Optionally, a single Key can be used to access multiple Locks. This is done by entering the [secret_key] information when adding that Key. The same [secret_key] information is then used when adding that Key to other Locks. The information is then used to generate the test responce. The secret key chosen by the administrator is the key information to be added
to the RPSD Key. If this option is not used, the RPSD Lock generates the secret key information randomly.
In any situation where the RPSD Key is already initialized (meaning from another Lock), the existing [secret_key] should be specified when adding the user.
In the syntax line above, a is the command and <user_id> is a unique identifier selected by the administrator. The user ID may be up to ten characters long and is not case sensitive. The [secret_key] is the
The RPSD Lock returns secret information and a test response when a user is added. This information is then used to initialize the RPSD Key, so make sure to note the information. Also, be careful to maintain the security of the information. The user ID will always be associated with that particular Key and its secret information and test response. A new RPSD Key must be initialized after the addition has been made to the Lock in order to gain access. See Chapter 2, Initializing an RPSD Key for the procedure.
Sample Command and Response Without Optional Secret Key:
> a KEY20
JPLock01 443 08/12/90 13:14:22 KEY20
>
Enter this secret key into the RPSD/Key unit
F37B 159D 6ABE 3E
Test Response is: 8119704
>
Sample Command and Response With Optional Secret Key:
> a KEY20, F37B159D6ABE3E
JPLock02 444 08/14/90 01:57:43 KEY21
>
Enter this secret key into the RPSD/Key unit
F37B 159D 6ABE 3E
Test Response is: 4296425
>
