If your organization has bought a certificate, or you have your own way of generating certificates, you can upload it. Browse to find the certificate file.
Browse to find the private key file that accompanies your certificate.
If your private key is stored in an encrypted format, you must enter the password here so that you can upload the key to the MCU.
You can upload a 'trust store' of certificates that the MCU will | Note that uploading a |
use to verify the identity of the other end of a TLS connection. | new trust store |
| replaces the existing |
The trust store must be in '.pem' format. | store. |
|
|
Choose to what extent the MCU will verify the identity of the | The trust store contains |
far end for a connection: | 'master' certificates that |
| can be used to verify |
: all outgoing connections are | the identity of a |
permitted to proceed, even if the far end does not | certificate presented by |
present a valid and trusted certificate. | the far end. |
: outgoing connections are | Outgoing connections |
only permitted if the far end has a certificate which is | |
trusted. | are connections such as |
: outgoing | SIP calls which use |
connections and incoming connections for SIP calls | TLS. |
| |
using TLS must have a certificate which is trusted |
|
otherwise the MCU will not allow the connection to |
|
proceed. |
|
180
