Reference11r1:Certificate names and trust relationships: Difference between revisions
Jump to navigation
Jump to search
| Line 16: | Line 16: | ||
;Certificate of the Device: | ;Certificate of the Device: | ||
* trusted by the browser | * trusted by the browser | ||
* CN or DNS name in the certificate has to match the host name or the IP address from the requested URL | * CN or DNS name in the certificate has to match the host name or the IP address from the requested URL | ||
;Certificate of the browser: | ;Certificate of the browser: | ||
not needed | not needed | ||
Revision as of 12:41, 29 April 2015
Applies To
This information applies to
- all innovaphone devices from V11r1
Overview
In TLS connections certificates are used for validating the identity of the server, or optionally the client as well. The certificate validation involves the following two main types of checks:
- Trust
- Is the certificate itself in the trust list? Is any of the CAs in the certificate chain in the trust list?
- Naming
- Does one of the names in the certificate match the name of the remote endpoint? For example if you open
https://www.example.comthe web browser checks if the certificate contains "www.example.com" as a name.
This article summarizes the requirements to trust relationships and certificate names in different scenarios.
HTTP / Websocket access from a web browser
- Certificate of the Device
- trusted by the browser
- CN or DNS name in the certificate has to match the host name or the IP address from the requested URL
- Certificate of the browser
not needed
Registration using H323/TLS
Authentication using username and password
- Certificate of the PBX
no requirements
- Certificate of the Phone
no requrements
Authentication using certificate
- Certificate of the PBX
no requirements
- Certificate of the Phone
- trusted by the PBX
- contains the registration name or the hardware ID (e.g. 0090332f688a or IP222-2f-68-8a) if no registaion name is configured