Friday, September 10, 2021

Server properties certificate

Use this tab to specify the certificate that is used by the server.

Server certificate

The certificate that is currently used by the server for Transport Layer Security (TLS) or Transport Layer Security with mutual TLS (MTLS) authentication.

Select certificate

Displays a list of certificates that are installed on the computer. The certificate that you select from the list is provided by the server in response to authentication challenges from clients or servers that send messages to this server.

Delete certificate

Removes the certificate so that it is no longer used by this server for TLS or MTLS. When you click Delete Certificate, the server no longer has a certificate assigned for MTLS, but the certificate is not deleted from the computer.

Learn More Online

Click to expand or collapse

You must assign a certificate to each server role in order for it to accept connections that require MTLS, such as those from other servers running Office Communications Server.

If your deployment is a Standard Edition server or an Enterprise pool in the consolidated configuration, the certificate configuration applies to all pool server roles collocated on the computer, including the Web Conferencing Server, the A/V Conferencing Server, the Web Components Server, and the Application Sharing Conferencing Server. If your deployment is an Enterprise pool in an expanded configuration, you must configure the certificate for the Web Conferencing Server, the A/V Conferencing Server, the Web Components Server, and the Application Sharing Conferencing Server individually.

Note:  If the default certificate does not include the name of the local computer, clicking the Certificate tab of the properties sheet for the Front End Server generates a warning stating that making any changes to the certificate may mean that other clients or servers will be unable to connect to this server.

For details, see the Operations section of the Office Communications Server Technical Library.

No comments:

Post a Comment