Home
Welcome to the HCL Sametime® 11.6 administration documentation
Administering
This section provides information on administering HCL Sametime 11.6 environments.
Managing Sametime Meetings
This topic explains the features you can enable or disable for meetings. Currently, the settings that you can change are global settings that apply to the entire server. User policies cannot control the settings.
Managing user sign-on
You can control how long your Sametime meeting credentials are maintained to reduce the number of times you have to sign-in.

Welcome to the HCL Sametime® 11.6 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.6 and Sametime® Meetings 11.6.
- Checklist to deploy Sametime
  This section provides information on reviewing the checklist to deploy the Sametime clients.
- Encryption usage in Sametime
  HCL® Sametime® uses several types of encryption to protect data.
- Planning
  This section describes the system requirements and server configurations needed for HCL Sametime 11.6.
- Installing
  This section provides information on installing and configuring the servers for HCL Sametime 11.6.
- Configuring
  This section provides information on configuring the servers for HCL Sametime 11.6.
- Securing
  This section provides information on securing HCL Sametime 11.6 environments.
- Administering
  This section provides information on administering HCL Sametime 11.6 environments.
  - Managing Sametime clients
    This section provides information on managing HCL Sametime clients.
  - Starting and stopping servers
    This section provides information on starting and stopping HCL Sametime 11.6 servers.
  - Managing policies
    Sametime policies allows administrators to control user access to features.
  - Configuration files
    There are a number of configuration files that a backup copy should be retained after the server configuration is complete.
  - Adding additional Sametime administrators
    Sametime Community server is installed on top of a Domino server. There are some administration and installation tasks that must be performed using the HCL Notes Client or HCL Notes Administrator client.
  - Enabling multi-tenancy
    Multi-tenancy allows multiple organizations to be part of the HCL Sametime® community. With multi-tenancy, Sametime users can chat, add users and groups to contact lists, and have awareness of users in their organization or in other organizations that are configured to be visible to them.
  - MongoDB
    This section provides information relating to administering MongoDB.
  - Disabling persistent chat and MongoDB requirements
    HCL Sametime 11.6 deploys with persistent chat enabled which requires MongoDB. It is possible to remove the MongoDB requirement if persistent chat and chat logging is disabled.
  - Managing Sametime Meetings
    This topic explains the features you can enable or disable for meetings. Currently, the settings that you can change are global settings that apply to the entire server. User policies cannot control the settings.
    - Disabling Guest Access
      You can disable guest access and remove the option from the meeting attend page.
    - Configuring Live Streaming
      If you have a high number of users that need to attend a meeting without two-way interaction, you can live stream the conference to YouTube. It will only be a listen and watch experience for attendees in the live stream. The users will attend this meeting using a YouTube URL. Most of the live stream requirements are on the YouTube account that belongs to the user who moderates the meeting. In the context of YouTube live streaming, consider the Sametime Meeting server as an “encoder” for YouTube. There is no requirement to install additional software.
    - Increasing Active Cameras | Videos
      The default allowed active cameras is 5, with the most recent active cameras displaying.
    - Managing Recording
      You can control how long meeting recordings are available and also disable the recording feature.
    - Managing user sign-on
      You can control how long your Sametime meeting credentials are maintained to reduce the number of times you have to sign-in.
  - Changing user names
    When you change user or group names in the directory, the change is not reflected in HCL® Sametime Community Server databases. In order to synchronize the directory names with the names in the Community Server databases, you must run the name conversion utility.
- Uninstalling Sametime
  In the event that Sametime must be uninstalled, follow these steps to uninstall the Community, Proxy, and Meetings servers.
- Troubleshooting
  Troubleshooting and Support
- Migrating and Upgrading
  This section provides information on migrating and upgrading from an earlier Sametime release.
- Notices

Managing user sign-on

You can control how long your Sametime meeting credentials are maintained to reduce the number of times you have to sign-in.

About this task

A token is maintained by the meeting sever to control how often you sign-in to your Sametime Meeting. The default value is 30 days. You can modify this value or turn off the feature by including the JWT_REFRESH_DURATION_DAYS environment variable in the YAML file. You can specify any number of whole days to retain login credentials. To disable this feature, set the value to 0.

Note: When you modify the docker-compose.yml file, follow the syntax rules for YAML files to prevent coding errors. When you modify the YAML file, the indentations of entries are spaces, not tab characters.

Managing user sign-on in Docker

Procedure

Edit the docker-compose.yml file and locate the auth section within the file.
The file is in the root directory .
Add the JWT_REFRESH_DURATION_DAYS environment variable.
Specify the duration in this format environment_variable=number_of_days.
```
JWT_REFRESH_DURATION_DAYS=number_of_days
```
The following example shows the auth section with the JWT_REFRESH_DURATION_DAYS environment variable set to 10 days.

Run the following commands for changes to activate the YAML file.


docker-compose down 
delete jitsi-config folder
docker-compose up -d

Managing user sign-on in Kubernetes

About this task

You can change settings temporarily or permanently. To temporarily change the setting, run the following command to change the setting in a deployed environment:

kubectl set env deploy/auth JWT_REFRESH_DURATION_DAYS=number_of_days

To permanently change the setting, complete the following steps:

Procedure

Edit the deployment.yaml file, which contains the auth environment variables.
You can find the file in the helm/charts/auth/templates directory.
Add the JWT_REFRESH_DURATION_DAYS environment variable.
Specify the duration in this format environment_variable: number_of_days.
```
name: JWT_REFRESH_DURATION_DAYS value: number_of_days
```
The following example shows the auth section with the JWT_REFRESH_DURATION_DAYS environment variable set to 10 days.

Run the following commands to activate the YAML:


helm uninstall sametime-meetings
helm install sametime-meetings

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.