Avaya DECT R4 Installation And Administration Manual page 78

Installing and operating the IPBS and IPBL
Secure Web Access (https)
For IP-DECT devices
To ensure secure communications, https access should be enabled.
●
Correspondingly, http access should be disabled
●
For more information see
TLS Certificates.
Security in Web-based applications rely on cryptography. Cryptographical systems are only as
secure as their keys. Key Management a critical and often neglected concern. TLS Certificates
have emerged as a clever way of managing large scale key distribution.
Certificate handling options
1. Default Device certificate
This certificate is a self-signed certificate supplied with the device. Self-signed certificates
provide only encryption, not authentication.
For more information, see
2. Self-signed certificates
This certificate is for customers who do not plan to have their certificates signed by public
or private CAs. Self-signed certificates provide encryption but do not provide
authentication in all cases.
For more information see
3. Certificates signed by a Certificate Authority (CA)
These certificates have two options:
a. Certificates signed by the customer's own CA. Customers possessing the knowledge
and infrastructure to house their own CA can build an internal enterprise CA, enabling
them to sign or approve their own certificate requests. This would make the customer
a private CA.
b. Certificates signed by a trusted public third-party entity/organization. Only about a
dozen issuers have the authority to sign certificates for servers worldwide. An example
is VeriSign. To use a public CA for certificate approvals, you must connect the
IP-DECT system to the Internet and obtain a fully qualified domain name.
For more information see
78
Avaya DECT R4 - Installation and Maintenance Guide
Configuring the HTTP settings
Default device certificate
Self-signed certificates
Certificate Signing Request (CSR)
on page 131.
on page 135.
on page 135.
on page 137.
02/2016