Skip to content

Server configuration

See also: Client configuration file.

You configure a containerized MultiTaction Canvus Server mainly through environment variables in podman-compose.yml. You do not need to edit files inside the container.

Advanced users can also edit the mt-canvus-server.ini configuration file. In the container deployment it is on the host at /canvus-data/config/mt-canvus-server.ini. If the file does not exist when the container starts, the container creates it from the built-in template.

Standalone installations (Linux .deb and Windows MSI) are configured only through mt-canvus-server.ini. Some settings can also be changed in the web admin area, see Settings you can also change in the web UI.

Environment variables

Edit podman-compose.yml and set variables under the canvus service's environment: block.

After changing any variable, restart the containers:

sudo podman-compose down
sudo podman-compose up -d

Required variables

Variable Description Example
CANVUS_EXTERNAL_URL Public URL clients use to reach the server https://canvus.example.com
CANVUS_ADMIN_EMAIL Email address for the initial admin account admin@yourcompany.com
CANVUS_ADMIN_PASSWORD Password for the initial admin account a-strong-admin-password
POSTGRES_PASSWORD Database password (must match postgres service) a-strong-database-password

Note

CANVUS_ADMIN_EMAIL and CANVUS_ADMIN_PASSWORD are only used on first startup to create the initial admin account. Changing them after first startup has no effect.

Optional variables

Variable Description Default
CANVUS_LICENSE_KEY Activation key. The container activates it once, on first startup, right after it creates the initial admin account. To activate later, use the admin web UI or --activate. empty
CANVUS_HTTPS_PORT HTTPS port inside the container. Used when SSL is enabled. 443
CANVUS_SSL_ENABLED true turns on HTTPS and the HTTP-to-HTTPS redirect. false turns both off and the server accepts plain HTTP only. When the variable is not set, the value in mt-canvus-server.ini is kept. true (in the shipped compose file)
CANVUS_HTTP_PORT Port the server listens on when CANVUS_SSL_ENABLED is false. When it is not set, [system] port in mt-canvus-server.ini is kept. It has no effect when SSL is enabled: the HTTP redirect always listens on port 80 inside the container. To use another host port for the redirect, change the port mapping, for example "8080:80". not set
CANVUS_HOSTNAME Host name used to build the external URL when CANVUS_EXTERNAL_URL is empty (https://<host> or https://<host>:<port>, or http:// when SSL is off). It is also the name in the self-signed certificate the container generates when no certificate exists. not set
POSTGRES_HOST Database host name postgres
POSTGRES_PORT Database port 5432
POSTGRES_DB Database name canvus
POSTGRES_USER Database user canvus
SESSION_SECRET Secret that signs web-client session cookies. See Web-client session secret. generated
CANVUS_WEBRTC_ENABLED, CANVUS_WEBRTC_MEDIA_URL WebRTC video streaming, which is off by default. See Configure WebRTC video streaming. not set
CANVUS_CANVAS_CALL_ENABLED false turns the canvas call off. The container writes it to [system] canvas-call-enabled at every start. When the variable is not set, the value in mt-canvus-server.ini is kept. not set (the call is on)

The POSTGRES_* values must match the postgres service in the same compose file.

Example podman-compose.yml environment block

services:
  canvus:
    environment:
      CANVUS_EXTERNAL_URL: https://canvus.example.com
      CANVUS_ADMIN_EMAIL: admin@yourcompany.com
      CANVUS_ADMIN_PASSWORD: a-strong-admin-password
      POSTGRES_PASSWORD: a-strong-database-password
      # CANVUS_LICENSE_KEY: XXXX-XXXX-XXXX-XXXX
  postgres:
    environment:
      POSTGRES_PASSWORD: a-strong-database-password

Settings the container rewrites at every start

The container entrypoint writes these keys into mt-canvus-server.ini each time the container starts, so editing them in the file has no lasting effect in a container deployment:

  • [sql] hostname, port, databasename, username, password (from the POSTGRES_* variables)
  • [certificates] certificate-file, certificate-key-file, certificate-chain-file (always the files in /canvus-data/certs)
  • [system] log-path, [content] root and [backup] root (the mounted folders)
  • [reverse-proxy] web-client-path and session-secret
  • [system] external-url, when CANVUS_EXTERNAL_URL or CANVUS_HOSTNAME is set
  • [system] ssl-enabled, http-redirect-enabled and port, when CANVUS_SSL_ENABLED, CANVUS_HTTPS_PORT or CANVUS_HTTP_PORT is set
  • [system] canvas-call-enabled, when CANVUS_CANVAS_CALL_ENABLED is set to true or false
  • [webrtc] enabled, when CANVUS_WEBRTC_ENABLED is true, and media-service-url, when CANVUS_WEBRTC_MEDIA_URL is also set

The entrypoint also comments out any [reverse-proxy] dashboard-url line. Change these settings through the environment variables instead. Every other key in the file is kept as you set it.

About mt-canvus-server.ini

Each Canvus Server has two versions of the configuration file:

  • A template lists the configuration settings with comments and defaults, for reference. The .deb package installs it as /etc/MultiTaction/canvus/mt-canvus-server.ini.template, and the Windows MSI as installer\mt-canvus-server.ini.template in the installation folder. When you update Canvus Server, the template is replaced with the new version.
  • A working version, mt-canvus-server.ini, configures the server. The working version is kept when you update Canvus Server. After updating, add any new settings you need to the working version yourself.

Note

When you configure the Canvus server, always edit the working version of the configuration file.

See File locations for default locations of the configuration file.

The server reads the file from these locations, in this order:

  1. The file named with the --server-config <filename> command-line option.
  2. The file named in the MT_CANVUS_SERVER_CONFIG environment variable.
  3. The default location: /etc/MultiTaction/canvus/mt-canvus-server.ini on Linux, %PROGRAMDATA%\MultiTaction\canvus\mt-canvus-server.ini on Windows.

The Windows service always uses the default location.

Use forward slashes in Windows paths

Write Windows paths in the file with forward slashes, for example C:/ProgramData/MultiTaction/canvus/certs/server.cert.pem.

Specify external URL

For Canvus server to display correct links to shared canvases, it needs to know the URL under which it is reachable by your users. For example, https://canvus.example.com.

[system]
; URL on which Canvus will be reachable. If empty, will be set to use a
; detected hostname and system/port with scheme set to HTTPS if system/ssl-enabled is
; true (otherwise HTTP).
; DEFAULT: empty
; external-url=

Important

Single sign-on needs external-url to be set to the address users type in their browsers. Canvus builds the sign-in redirect URI from it. See Set up single sign-on with Microsoft Entra ID.

Server name

[system]
; Name of this server. Shown in browser titles and email sender names.
; Also editable in Admin > Settings > General.
; DEFAULT: empty
; server-name=

Specify database

You must provide the server with details about the database that you set up during server installation. The standalone installers and the container fill in these values for their bundled database.

[sql]
; Settings for PostgreSQL data storage

; Host name or address of the PostgreSQL server.
; DEFAULT: localhost
; The Linux package writes 127.0.0.1, the Windows MSI localhost and the
; container postgres (the name of the database container).
; hostname=localhost

; PSQL server port to use
; DEFAULT: 5432
; The Linux package uses 5433 for its bundled database.
; port=5432

; Name of the database to use
; DEFAULT: empty
; databasename=

; Set the username for DB login.
; DEFAULT: empty
; username=

; Set the password for DB login.
; DEFAULT: empty
; password=

; Windows only: folder of the bundled PostgreSQL installation that the
; server loads its database client libraries from. The Windows MSI writes
; this value; change it only if you move the installation.
; DEFAULT: empty
; postgresql-path=

Note

Canvus server must be restarted for these changes to take effect.

The connection to the database is not encrypted, and there is no [sql] setting for SSL. Canvus Server cannot connect to a PostgreSQL server that requires SSL. See Server database.

Define accepted connections

Canvus server uses a single port to listen for connections. It accepts Canvus clients using proprietary TCP/SSL protocol and web browsers accessing the web UI using HTTP(S). The arriving traffic is multiplexed based on protocol.

Canvus can optionally redirect HTTP traffic from port 80 to the port it listens SSL/HTTPS connections for.

If you enable encrypted SSL connections, you may also want to set up certificates.

[system]
; The address where the server will listen for the connections
; DEFAULT: 0.0.0.0 (all available networks)
; address=0.0.0.0

; Port where the server will listen for the connections
; DEFAULT: 80 for TCP protocol
; DEFAULT: 443 for SSL protocol (if system/ssl-enabled is true)
; port=443

; Enable encrypted HTTPS or TLS connections to the server. If disabled, only
; unencrypted HTTP or TCP connections are supported.
; DEFAULT: true
; ssl-enabled=true

; If enabled, the server listens to HTTP connections on port 80 and redirects
; them to the SSL port. This is only used if system/ssl-enabled is true and
; system/port is different from 80.
; DEFAULT: true when system/ssl-enabled is true and system/port is not 80,
; otherwise false
; http-redirect-enabled=true

The server checks these values at startup and refuses to start when:

  • http-redirect-enabled=true is set while ssl-enabled=false. Set http-redirect-enabled=false when you turn SSL off.
  • http-redirect-enabled=true is set while port=80.

Tip

Use encrypted SSL connections only.

Note

Canvus server must be restarted for these changes to take effect.

Connection password

You can require Canvus clients to enter a shared password before they connect to the server.

[system]
; Set the password that is required for connecting to this server.
; If the password is empty, then no password is required.
; The password cannot contain semicolon, or quotation marks.
; DEFAULT: empty
; connection-password=

Log files

[system]
; Directory for storing server log files. If empty, the log is written to
; standard output only and the server writes no log files.
; DEFAULT: logs folder under the server's data folder
; ($HOME/logs on Linux, %PROGRAMDATA%\MultiTaction\canvus\logs on Windows)
; The Linux package, the Windows MSI and the container set it to a
; logs/server folder.
; log-path=

See Audit log and server logs for the file names and how to read them.

Setup certificates for encrypted connections

If you want to encrypt connections between Canvus clients and the server, or between browsers and the Canvus dashboard, you need a digital certificate and specify its location on the Canvus server.

Note

All files in the [certificates] block should be X.509 certificates in .pem format.

[certificates]
; SSL certificate settings, shared between Canvus Connect server and the
; web UI. If all fields in this sections are left empty but SSL is enabled, a
; new self-signed certificate is created automatically.

; Certificate file name (.pem). This is the digital certificate issued by
; your Certificate Authority (CA). Make sure the certificate common name
; matches the domain name in system/external-url.
; DEFAULT: empty
; certificate-file=

; Certificate private key file name (.pem).
; DEFAULT: empty
; certificate-key-file=

; Certificate chain file name (.pem). This is the intermediate certificate
; issued by your CA.
; DEFAULT: empty
; certificate-chain-file=

Tip

If you leave certificate-file and certificate-key-file empty but set system/ssl-enabled to true, Canvus will automatically generate self-signed certificates for you during startup and use them automatically.

The automatically generated certificates are placed in the following locations:

  • Windows: %PROGRAMDATA%\MultiTaction\canvus\server\certificates
  • Ubuntu: /etc/MultiTaction/canvus/server/certificates

Note

Canvus server must be restarted for these changes to take effect.

However, if you are later renewing existing certificate files on disk (e.g. Let's Encrypt), you can run mt-canvus-server --reload-certs to notify the server to reload the certificates and avoid having to restart it.

Certificate checks at startup

From Canvus Server 26.08.0, when SSL is enabled the server writes the certificate, key and chain file paths to its log at startup, with the certificate's subject, subject alternative names and expiry date. It logs a warning when the certificate expires within 30 days and an error once it has expired.

From Canvus Server 26.09.4, the server stops at startup with the error SSL certificate-key-file … contains no private key when the key file has no private key. Other certificate or key problems, such as a key that does not match the certificate, are reported once in the log.

Define authentication methods

Canvus server supports multiple authentication methods for users. You can also configure which authentication methods can be used to sign up.

Tip

Some of these settings are also in the web UI, see Settings you can also change in the web UI.

Single sign-on is not set in this file

Canvus Server 26.11.1 removed SAML. Single sign-on with OpenID Connect (Microsoft Entra ID or another provider) is configured in Admin > Authentication in the web UI and stored in sso-config.json, not in mt-canvus-server.ini. It needs external-url to be set. The [saml] section and the saml-enabled and saml-sign-up-enabled keys are ignored. See Set up single sign-on with Microsoft Entra ID.

[authentication]
; Enables authentication using email and password
; DEFAULT: true
; password-enabled=true

; Enables creation new local accounts
; Applies only if password authentication enabled
; DEFAULT: true
; password-sign-up-enabled=true

; Enables QR code authentication
; DEFAULT: true
; qr-code-enabled=true

; Comma separated list of domains allowed for creating new accounts (both single sign-on and local)
; Wildcards are allowed in the domain names
; Example: sign-up-allow-list=multitaction.com,gmail.com,*.gov
; DEFAULT: *
; sign-up-allow-list=*

; Number of distinct passwords a user must create before they can reuse a
; previous password. Set to 0 to allow a user to reuse any password.
; DEFAULT: 0
; password-history-count=0

; The number of days until a user password expires and must be changed.
; Applies to password sign-in. Set to 0 to never expire passwords.
; DEFAULT: 0
; max-password-age=0

; When enabled, any user signing up for an account has to be approved
; by an administrator before they can sign in. It also applies to accounts
; created by single sign-on.
; DEFAULT: false
; require-admin-approval=false

Local accounts need email to confirm new addresses and to reset passwords. See Email (SMTP) setup.

Password policy

Local-account passwords are checked against a configurable complexity policy when users choose or change a password, and when an administrator sets one in the web UI or through the API. By default, only a minimum length is enforced. A mix of letters, numbers and symbols is not required unless you configure it:

[password-security]
; The minimum number of characters passwords must have.
; Set to 0 or empty for no limit.
; DEFAULT: 8
; min-length=8

; The minimum number of lowercase characters a password must have.
; DEFAULT: 0
; min-lowercase=0

; The minimum number of uppercase characters a password must have.
; DEFAULT: 0
; min-uppercase=0

; The minimum number of numeric characters a password must have.
; DEFAULT: 0
; min-numeric=0

; The minimum number of symbol characters, for example !@#$%^&*, a
; password must have.
; DEFAULT: 0
; min-symbol=0

; A password can not contain more than N repeating characters.
; Set to 0 for no limit.
; DEFAULT: 0
; max-repeats=0

; A password can not contain any ascending or descending sequence of
; more than N alphanumeric characters. Set to 0 for no limit.
; DEFAULT: 0
; max-sequence=0

; The user name (email address) must be excluded from the password.
; DEFAULT: true
; exclude-username=true

To require passwords to contain letters, numbers and symbols, set min-lowercase, min-uppercase, min-numeric and min-symbol to at least 1.

Passwords set from the command line

Passwords set with the server's command-line user commands (--create-user, --create-admin, --change-password) are not checked against this policy. This includes the initial admin account that the container creates from CANVUS_ADMIN_PASSWORD. Choose those passwords to meet your policy yourself.

Email (SMTP)

The server sends email to confirm new email addresses and to reset passwords. The [smtp] and [mail] sections configure it. See Email (SMTP) setup for the full procedure.

[smtp]
; SMTP server host. Email is disabled while this is empty.
; DEFAULT: empty
; host=

; SMTP server port
; DEFAULT: 25
; port=

; SMTP server username
; DEFAULT: empty
; username=

; SMTP server password
; DEFAULT: empty
; password=

; SMTP connection security. Valid options are: none, tls, starttls.
; none      - Connection will not use TLS even if the SMTP host supports
;             STARTTLS extension.
; tls       - The connection will be encrypted using SSL or TLS immediately
;             after connecting to the SMTP host.
; starttls  - The connection will attempt to use SSL/TLS if the server supports
;             the STARTTLS extension. If the SMTP server does not support it,
;             messages will not be sent.
; DEFAULT: none
; security=

; Trust self-signed SSL certificate on SMTP host.
; DEFAULT: false
; allow-self-signed-certificate=

[mail]
; Email address of the sender for all email the server sends.
; Email is disabled while this is empty.
; DEFAULT: empty
; sender-address=

; Name of the sender for all email the server sends.
; DEFAULT: empty
; sender-name=

; Email address of the Reply-To address for all email the server sends.
; DEFAULT: empty
; reply-to-address=

; Display name of the Reply-To address for all email the server sends.
; DEFAULT: empty
; reply-to-name=

Automatic pinning

[widget]
; If set, an unpinned widget is pinned after it has not been scaled or moved
; for the specified number of seconds.
; If zero, the widget is never auto-pinned.
; DEFAULT: 0
; auto-pin-after=0

The server reads this value at startup. Restart the server after changing it.

Default canvas colors

From Canvus Server 26.6.2, you can set the color palettes that new canvases on this server start with.

[canvas]
; Comma-separated hex colors. Invalid entries are skipped. An empty list,
; or a list with no valid entries, falls back to the built-in palette.
; Connector colors always follow the pen palette.
; DEFAULT: built-in palette
; default-pen-color-presets=#e7e7f2,#000000,#0539db,#f7f700,#08c41a,#f20000
; default-note-background-color-presets=#3aaa34,#1d71b8,#fcea0f,#e6332a,#662583,#ffffff

The server reads the palettes at startup. Canvases created after a restart use them. Existing canvases keep their own palettes.

Backups

[backup]
; Default folder for server backups. Set to empty to disable the automatic
; backup on software update.
; DEFAULT: /var/lib/mt-canvus-server/backups on Linux,
; %PROGRAMDATA%\MultiTaction\canvus\backups on Windows
; root=

See backup-and-restore.

Codice folders

Canvus allows content to be stored in special folders associated with Codice markers. These folders are called Codice folders.

This feature is always enabled on the Canvus server. No configuration steps are required to enable it. Some behavior of the feature can be controlled by modifying settings in the following settings.

Enforce Codice folder passwords

Codice folders can be protected by a password that must be entered before the contents of the folder can be accessed by a user. The password can be made mandatory by adjusting the following setting:

[system]

; Set to true if all newly-created Codice folders must be protected by a
; password.
; DEFAULT: false
; enforce-codice-folder-password=false
; (The legacy key name "enforce-personal-folder-password" is accepted as a deprecated alias.)

Note

This setting has no effect on any Codice folders on the server that were created before the setting was enabled.

Enforce Codice folder registration

A Codice folder can be either anonymous or registered. Anonymous Codice folders are only linked with a specific Codice card. Registered Codice folder has additionally the user's name and email address associated with it.

To disallow anonymous Codice folders, the registration can be made mandatory by adjusting the following setting:

[system]

; Set to true if all newly-created Codice folders must be registered with a
; valid name and email address. If false, Codice folders can be anonymous
; and just attached to a Codice marker.
; DEFAULT: false
; enforce-codice-folder-registration=false
; (The legacy key name "enforce-personal-folder-registration" is accepted as a deprecated alias.)

Note

This setting has no effect on any Codice folders on the server that were created before the setting was enabled.

Info

Configure WebRTC video streaming

WebRTC video streaming is off by default. [webrtc] enabled defaults to false, and the shipped podman-compose.yml has the canvus-media service and the CANVUS_WEBRTC_* variables commented out. Leave it off unless MultiTaction support asks you to turn it on.

When it is on, the Canvus server relays WebRTC signaling between desktop clients and a separate canvus-media service. Video traffic flows between the clients and canvus-media, not through the Canvus server.

[webrtc]
; Enable WebRTC video streaming. When enabled, the server relays WebRTC
; signaling messages between desktop clients and the canvus-media service.
; Requires a running canvus-media service.
; DEFAULT: false
enabled=false

; URL of the canvus-media WebSocket signaling endpoint. The server connects
; to this URL to relay signaling. If enabled=true and this is empty, the
; server logs an error and keeps WebRTC off.
; DEFAULT: empty
; media-service-url=

Note

In the container deployment, CANVUS_WEBRTC_ENABLED and CANVUS_WEBRTC_MEDIA_URL in podman-compose.yml set these values. When CANVUS_WEBRTC_ENABLED is true, the entrypoint writes enabled=true into the file at every start, and media-service-url from CANVUS_WEBRTC_MEDIA_URL when that is set.

Canvas call

The canvas call lets everyone who has the same canvas open talk to each other and see each other. See Canvas call for what people see. The server forwards each client's call audio and head shots to the other clients on the same canvas, over the connection each client already has, so the call needs no extra port, no UDP and no extra service.

[system]
; Canvas call: people viewing the same canvas can see and hear each other.
; The server forwards each person's call audio and video to the others on
; that canvas, over the connection the client already has to this server (no
; extra port or service). When false, the server tells clients the canvas call
; is off and drops any call media it receives. Only clients new enough to offer
; the canvas call are affected. Takes effect when the server is restarted.
; DEFAULT: true
; canvas-call-enabled=true

Set canvas-call-enabled=false to turn the call off for every canvas on this server. To turn it off on single client installations instead, see Canvas call administration. The server can read the call it forwards; see privacy.

Configure the reverse proxy and web-client serving

The Linux package, the Windows MSI and the container all serve the web client from a gateway built into the server process. Earlier releases used a separate Node.js web-proxy process reachable at dashboard-url. That process no longer runs, nothing listens on a separate port for dashboard-url, and leaving dashboard-url unset does not break the web UI.

[reverse-proxy]
; URL of an external web-proxy. Used only when web-client-path is empty.
; Leave it unset: web-client-path takes precedence.
; dashboard-url=

; Folder holding the web-client files. When set, the built-in gateway serves
; the web client and handles web sign-in itself.
; The Linux package and the container set /opt/canvus/web-client/dist; the
; Windows MSI sets the web-client folder in its installation folder.
web-client-path=/opt/canvus/web-client/dist

; Secret that signs web-client session cookies. The Linux package, the
; Windows MSI and the container each generate one at install or first start.
; See "Web-client session secret" below.
; session-secret=

; Signaling URL of the canvus-media service for WebRTC video in the web
; client. Leave empty while WebRTC video streaming is off.
; DEFAULT: empty
; canvus-media-url=

REST API streams

The [rest-api] section sets the keepalive interval of REST API ?subscribe streams. Integrations that follow changes with ?subscribe receive an empty line at this interval while nothing else is sent, so proxies and clients do not close the connection as idle.

[rest-api]
; Seconds between the empty keepalive lines on an open ?subscribe stream.
; Use a whole number of 1 or more.
; DEFAULT: 15
; keepalive=15

Restart the server to apply a change. Raise the value only if a proxy or client needs fewer idle writes, and keep it below the read timeout of the integrations that use streams.

Warning

Do not set keepalive to 0, to a negative number or to text, and do not leave it empty. In Canvus Server 26.11 such a value makes every ?subscribe stream fail with 502 Proxy error, while ordinary API requests keep working.

Web-client session secret

The in-process Go gateway signs browser session cookies with a secret value, stored as [reverse-proxy] session-secret in mt-canvus-server.ini.

  • Linux package: generated once at install, kept in /var/lib/canvus/.session-secret and written into the configuration file.
  • Windows MSI: generated at install and written into the configuration file.
  • Container: at each start the entrypoint uses SESSION_SECRET from the container environment if it is set. Otherwise it reads, or generates, a secret file inside the container and writes the value into the configuration file.

Container: set SESSION_SECRET to keep sessions across updates

Without SESSION_SECRET, the generated secret lives inside the container, not on the /canvus-data volume. Recreating the container (podman-compose down then up, as in an update) generates a new secret and signs every user out. To keep sessions across updates, set SESSION_SECRET in podman-compose.yml to a long random value, for example the output of openssl rand -hex 32.

Treat the session secret as a secret

Anyone with the secret can forge valid sessions. Keep it out of version control, chat transcripts and screenshots, and protect the configuration folder with filesystem permissions. Include the configuration file in your backups.

Rotating the session secret

To invalidate all existing web-client sessions (for example, after a suspected leak or a departing admin):

  • Container: change SESSION_SECRET in podman-compose.yml (or, if you do not set it, leave it unset), then recreate the container with sudo podman-compose down and sudo podman-compose up -d.
  • Linux package and Windows MSI: replace the session-secret value in mt-canvus-server.ini with a new random value, then restart the server.

All users must sign in again.

Settings you can also change in the web UI

Administrators can change these settings in the web admin area. The server writes the change into mt-canvus-server.ini. See Admin web UI.

Web UI Setting
Admin > Settings > General: Server name [system] server-name
Admin > Settings > General: Allow public self-registration [authentication] password-sign-up-enabled
Admin > Settings > General: Require admin approval for new accounts [authentication] require-admin-approval
Admin > Settings > Email [smtp] and [mail]

The external URL is shown in Admin > Settings > General but you cannot change it there. Change it in the configuration file and restart the server.

Removed and renamed settings

Older configuration files may contain settings that Canvus Server no longer uses. The server checks for them at startup:

  • tcp/address, tcp/port, ssl/address, ssl/port, rest-api/address, rest-api/port and dashboard/address, dashboard/http-port, dashboard/https-port are replaced by [system] address and port. rest-api/enable-https and dashboard/enable-https are replaced by [system] ssl-enabled. If an old key has the same value as its replacement, the server logs a warning. If the values differ, the server logs Configuration option '<old>' has been superseded by '<new>' but now they have conflicting values and refuses to start. Remove the old key.
  • rest-api/auth-tokens, dashboard/enable-http, dashboard/json-api-enabled, dashboard/port, dashboard/admin_username, dashboard/admin_password and system/enforce-canvas-password have been removed. The server logs a warning and ignores them. Create access tokens in the web UI instead of rest-api/auth-tokens.
  • system/enforce-personal-folder-password and system/enforce-personal-folder-registration are accepted as aliases of the enforce-codice-folder-* keys. If both the old and new key are set to different values, the server refuses to start.

Advanced configuration settings

The Canvus server configuration file contains additional settings not documented in this manual. These settings are used to configure advanced Canvus server operations. You do not need to change these settings from their default values unless instructed to do so by MultiTaction support staff.