Configuration of extensions

TrueConf Directory

In the Extensions → TrueConf Directory section, you can configure integration of your TrueConf Server instance (a part of TrueConf Enterprise) with solution TrueConf Directory.

To do it, click on the Activate button. To disable integration, click on the Deactivate button.

In the large box below the table, the secret key will be generated.

If you want to learn more about TrueConf Directory extension, as well as how to purchase and set it up, please contact us in any convenient way.

We demonstrated TrueConf Directory features at ISE 2019.

Integration with DLP

If the Integration with DLP extension is activated in your TrueConf Server license, you will be able to configure connection to such a system and select the actions that should be performed when violations of information security rules are detected.

1. Extension activation. If the box is not marked and settings have not been saved with the Apply button, no checks will be performed.

2. DLP connection parameters: host (IP or FQDN without the http: / https: prefix), port and connection type (cloud or secure TLS connection).

3. System availability test. The test result will be displayed in the status line below.

   

4. Activation of text message verification. If the box is not checked, and no settings have been saved with the Apply button, no verification will be available.

5. ICAP request containing the fields that should be sent to a DLP system. The request format will depend on the specific system. Here, we have listed the variables used in the template, These variables will be replaced with specific values when data is sent for analysis.

6. Reset the ICAP request to the default template.

7. Discard the last changes that were not saved with the Apply button.

8. Actions with a message marked as unwanted by the DLP system. It is possible to replace the message with a text selected on the side of the DLP system. One can also specify a custom text for the message or leave the initial message unchanged. In the last case, users will receive all messages, but the logs of the DLP system will include records of unwanted messages.

9. Actions with an unwanted message if there is no connection with the DLP system. For example, it is possible to enter the text “No connection with the security system” so that no messages can be sent to recipients until the problem is solved.

10. DLP response waiting time. If connection with the system is disrupted, the time period specified here will have to expire until TrueConf Server responds when the first message is sent. It will follow the settings from step 9 (attempts will be made to restore the connection). Then, connection availability will be tested in background mode, In this case messages will be sent or blocked almost instantaneously.

    

11. Activation of file verification. If the box is not checked, and no settings have been saved with the Apply button, verification will be unavailable. Please note that file analysis and response may take some time depending on the file size since the file will be first uploaded on TrueConf Server and then sent to the DLP system.

12. ICAP request containing the fields that should be sent to the DLP system.

13. Reset the ICAP request to the default template.

14. Discard the last changes that were not saved with the Apply button.

15. Actions with a file marked as unwanted by the DLP system. It is possible to replace this file with the text specified on the DLP system. One can also specify a custom text message or make no changes. In the last case users will receive all files, but the logs of the DLP system will include records of unwanted files.

16. Actions with an unwanted file in case there is no connection with the DLP system. For example, it is possible to enter this text “No connection with the security system” so that no files could be sent to recipients until the problem is solved.

17. DLP system response waiting time. The logic similar to the one used for messages is applied here (check step 10).

18. Limitation on the number of participants in the group chat for sending their list to DLP.

19. Don’t forget to click the Apply button to save changes.

Variables in the templates of ICAP requests

• %body — request content (text message from the chat)

• %body_length — request content length (measured in bytes)

• %body_offset — request content offset in the encapsulated section (measured in bytes)

• %chat_id — unique GUID of the chat

• %chat_id_origin — %chat_id from which a message is forwarded (this field is empty if the message is not forwarded)

• %chat_title — chat name

• %chat_title_base64 — %chat_title in base64 format

• %content_length — the content length of the request (decimal, in bytes)

• %date — date in the ISO 8601 (opens new window) format

• %dst — the recipient’s full TrueConf ID presented as user@server

• %dst_base64 — %dst in base64 format (opens new window)

• %dst_user — the recipient’s login (part of TrueConf ID up to the @ character) with the domain specified as domain\user

• %dst_user_at_domain — the recipient’s login in the user@domain format ( @domain may be omitted if the recipient is in the main domain)

• %dst_user_at_domain_base64 — %dst_user_at_domain in base64 format

• %dst_user_base64 — %dst_user in base64 format

• %dst_user_no_domain — recipient’s login

• %dst_user_no_domain_base64 — %dst_user_no_domain in base64 format

• %host — the value taken from the Host field

• %port — the value taken from the Port field

• %server_name — the domain name of TrueConf Server

• %src — sender’s full TrueConf ID

• %src_base64 — %src in base64

• %src_user — sender’s login (part of TrueConf ID up to the @ character) with the domain specified as domain\user

• %src_user_at_domain — the sender’s login in the user@domainformat (@domain may be omitted if the sender is in the main domain)

• %src_user_at_domain_base64 — %src_user_at_domain in base64 format

• %src_user_base64 — %src_user in base64 format

• %src_user_no_domain — sender’s login

• %src_user_no_domain_base64 — %src_user_no_domain in base64 format

• %src_ip — sender’s IP address

Additional information is available for files:

• %filename — name of the file being sent

• %filename_base64 — %filename in base64 format

Mail plugins

This extension enables you to:

• Control the web version of Microsoft Outlook plugin that will be downloaded from your server

• Receive direct links for installing the Windows version of the Outlook add-on and Thunderbird plugin

• Customize a template invitation to a conference.

This extension is offered for free (including TrueConf Server Free as well).

On the Plugins tab, you can:

1. Download the xml file for installing the web version of the add-on (plugin) and update the current version on the server in the Outlook (web) section. The plugin installation link can be copied with the button and then distributed among the users of the corporate network (including the private network that does not have access to the Internet) so that these users could install the plugin directly from your TrueConf Server.

2. Copy the download link for the desktop version of the Outlook add-on with the button in the Outlook (for Windows) section and share it among users. They will be able to download the plugin from our website via the Internet. You can also distribute the application with the help of group policies since it is provided as an msi package.

To learn more about installation and features of desktop and web versions of the MS Outlook add-on, check out our knowledge base.

3. Copy the installation link for the Thunderbird plugin with the button in the Thunderbird section and share this link among users.

On the Settings tab, you can change the default text of the description which is added when a new event is created with the help of any TrueConf mail plugins. Here, you can enable PIN code to be added in the description (providing that PIN was set previously):

In the invitation template, one can use a group of constants similarly to the email templates available when configuring SMTP:

• %conf_name — name of the conference

• %conf_id — ID of the conference, e.g. \c\df0a2adebe

• %owner_name — display name of the conference owner

• %conf_url — the link to the conference page, e.g.,:

  https://example.com/c/CID

• Server administrator contacts parameters:

  • %admin_name — display name

  • %admin_email — email address

  • %admin_phone — phone number.