2N Access Unit - 2 N Access Unit Configuration Manual; ;

2N Access Unit Configuration Manual
91 / 134
•
•
•
You can export/import the encryption keys and location identifier to other 2NAccess Unit.
2NAccess Unitswith identical location names and encryption keys form so-called locations. In
one location, a mobile device is paired just once and identifies itself with one unique Auth ID (i.e.
a user AuthID can be copied from one 2NAccess Unitto another within a location).
Pairing
Pairing means transmission of user access data to a user personal mobile device. The user
access data can only be saved into one mobile device, i.e. a user cannot have two mobile devices
for authentication, for example. However, the user access data can be saved into multiple
locations in one mobile device (i.e. the mobile device is used as a key for more locations at the
same time).
To pair a user with a mobile device, use the user's page in the 2NAccess Unitphone book.
Physically, you can pair a user locally using the USB Bluetooth module connected to your PC or
remotely using an integrated Bluetooth module. The results of both the pairing methods are the
same.
The following data is transmitted to a mobile device for pairing:
Location identifier
Location encryption key
User Auth ID
Encryption Key for Pairing
An encryption key other than that used for communication after pairing is used in the pairing
mode for security reasons. This key is generated automatically upon the 2NAccess Unitfirst
launch and can be re-generated any time later.
Encryption Key Administration
The 2NAccess Unitcan keep up to 4 valid encryption keys: 1 primary and up to 3 secondary
ones. A mobile device can use any of the 4 keys for communication encryption. The encryption
keys are fully controlled by the system administrator. It is recommended that the encryption
keys should be periodically updated for security reasons, especially in the event of a mobile
device loss or intercom configuration leak.
Note
