Welcome to the HCL Sametime® 11.5 administration documentation
- Accessibility features for Sametime
  Accessibility features help users who have a disability, such as restricted mobility or limited vision, to use information technology products successfully. HCL® strives to provide products with usable access for everyone.
- What's new in HCL Sametime
  This section describes what's new in HCL Sametime® 11.5 and Sametime® Meetings 11.5.
- Checklist to deploy Sametime
  This section provides information on reviewing the checklist to deploy the Sametime clients.
- Planning
  This section describes the system requirements and server configurations needed for HCL Sametime 11.5.
- Installing
  This section provides information on installing and configuring the servers for HCL Sametime 11.5.
- Configuring
  This section provides information on configuring the servers for HCL Sametime 11.5.
- Securing
  This section provides information on securing HCL Sametime 11.5 environments.
  - Installing GSKit on Microsoft Windows
    To install GSKit on Microsoft Windows, follow the steps:
  - Installing GSKit on Linux
    To install GSKit on Linux, follow the steps:
  - Securing connections
    - Choosing the TLS Configuration Scope
    - Securing connections between Sametime Community and Sametime clients
    - Securing Server to Server Connections
    - Securing connections between Sametime Community and LDAP
      When Sametime is configured to connect to an LDAP server, the Sametime Community Server makes five separate connections to the LDAP server.
    - Securing the Sametime Proxy Server
  - Enabling Single Sign On
    The HCL Sametime Community server uses the web server security features of the Domino server. By default the Sametime server installer configures single sign on for Domino.
  - Enable Security in MongoDB
    To enable MongoDB securing, edit the mongod.conf file setting authorization: enabled.
  - Updating the Sametime Meeting Server TLS Certificates
    This section provides information on updating the Sametime Meeting Server certificates.
- Administering
  This section provides information on administering HCL Sametime 11.5 environments.
- Troubleshooting
  Troubleshooting and Support
- Migrating and Upgrading
  This section provides information on migrating and upgrading from an earlier Sametime release.
- Notices

Securing the Sametime Proxy Server

About this task

Replacing the self-signed certificate with a third party certificate

A third party certificate is recommended for deployments that include mobile devices.

Follow the steps in the knowledge article: How to create a new Java Keystore with a Third Party certificate for Sametime Proxy 11.

Changing the default HTTP/S ports

The Sametime 11 Proxy server default ports are 8080 (unsecure) and 8443 (secure).

To change the ports to 80 and 443, use this procedure.

In the folder you unzipped the Sametime proxy application, locate the "server.xml" file located in the conf subfolder.
Open the file using a text or xml editor.
Locate the two settings below –
<Connector port="8080" protocol="HTTP/1.1" connectionTimeout="20000" redirectPort="8443"/>

<Connector protocol="org.apache.coyote.http11.Http11NioProtocol" port="8443" maxThreads="200" scheme="https" secure="true" SSLEnabled="true" keystoreFile="conf/stproxy.keystore" keystorePass="sametime" clientAuth="false" sslProtocol="TLS"/>
Update the "port" values to 80 and 443:
<Connector port="80" protocol="HTTP/1.1" connectionTimeout="20000" redirectPort="443"/>

<Connector protocol="org.apache.coyote.http11.Http11NioProtocol" port="443" maxThreads="200" scheme="https" secure="true" SSLEnabled="true" keystoreFile="conf/stproxy.keystore" keystorePass="sametime" clientAuth="false" sslProtocol="TLS"/>
Save and restart the Sametime Proxy server and validate.

Disabling Early TLS

In the folder you unzipped the Sametime proxy application, locate the "server.xml" file located in the conf subfolder.
Open the file using a text or xml editor.
Modify the sslProtocol=”TLS” to sslProtocol=”TLSv1.2”.
<Connector protocol="org.apache.coyote.http11.Http11NioProtocol" port="8443" maxThreads="200" scheme="https" secure="true" SSLEnabled="true" keystoreFile="conf/stproxy.keystore" keystorePass="sametime" clientAuth="false" sslProtocol="TLS"/>
Modify to
<Connector protocol="org.apache.coyote.http11.Http11NioProtocol" port="8443" maxThreads="200" scheme="https" secure="true" SSLEnabled="true" keystoreFile="conf/stproxy.keystore" keystorePass="sametime" clientAuth="false" sslProtocol="TLSv1.2"/>

Rate this topic

5 stars 4 stars 3 stars 2 stars 1 star

Comment on this topic.

By clicking this box, you acknowledge that you are NOT a U.S. Federal Government employee or agency, nor are you submitting information with respect to or on behalf of one. HCL provides software and services to U.S. Federal Government customers through its partners immixGroup, Inc. Contact this team at https://hcltechsw.com/resources/us-government-contact. Do not include any personal data in this Comment box. Note: To report a problem or question about the product software, do not use this form. Instead, go to the HCL Software Support site.