Encryption keys for My2N app
Users can use the My2N application to connect to 2N devices. Communication between the My2N application and the device is always encrypted. Access Commander automatically manages the system pairing keys that are distributed on a WaveKey supporting device and ensure secure trusted pairing. The My2N application cannot authenticate a user without knowing the encryption key. The primary encryption key is automatically generated either upon the intercom first launch or as part of the intercom configuration in case of Access Commander administration. The key can be re-generated manually any time. Together with Auth ID, the primary encryption key is transmitted to the mobile device for pairing.
Note
Two key types are used in the system: pairing keys and access keys. The pairing keys help authenticate the My2N application with the device. The access keys define permissions to functions within a mobile application.
Go to .
Up to 4 access keys can be generated. When you attempt to generate the fifth key, Access Commander will warn you that the oldest key will be removed. The card shows the generation time for each key.
Click .
Tip
It is recommended that the pairing keys are re-generated once in a longer period of time (once a year, e.g.) for security reasons.
The generated key is automatically uploaded into My2N upon the first use of the mobile phone with the device paired earlier.
The generated key can be deleted by clicking 
.
Tip
Pairing using a QR code containing a public key is recommended for higher security. If no QR code is available, you can use PIN pairing.
Caution
QR code pairing is only supported for devices with HIP firmware 2.50.0 and higher (including the 3.0 series). The QR code may be displayed in an environment with Access Commander, but pairing on older HIP versions will only be successful if the PIN is used.
Note
If the My2N application has no access to any of the valid encryption keys, it cannot be used for user authentication. To restore the application functionality, it will be necessary to re-pair the application with the device connected to Access Commander and thus upload the valid encryption keys to the My2N application.
The access to the device depends on the access rights of the given user.