v/1.13.0 (develop)
|
Update to 1.13 in the same container - only from version 1.11.9 and later; When upgrading in a new container from a version lower than 1.11.9, first update the system to 1.11.9. Versions 1.12 and 1.13 change the types of date-time fields in ClickHouse tables, mask psk in local.cfg.json and encrypt some secrets; versions before 1.11.9 do not read this data. Rollback from 1.13 — restoring backups and running 1.12 or 1.11.9 and later: Rollback to version 1.11. |
Platform
-
Updated the Debian version in the container to 13.
-
Updated OTP (erlang) version to 29.1.
-
Installation key: domain secrets (storage passwords, cloud account keys, connection strings,
survival_optionsreservation tokens) are encrypted with a key created during installation and stored in the protected:SYNC/securedirectory (not accessible via API and scripts); key files are copied to the local directory of each server; deletion from:SYNCdoes not affect the copy. Parameter general.crypto_kid. In existing systems, the key is created with theerainstaller.sh keygencommand; without the parameter, the encryption is the same. -
Domain secrets (storage passwords, settings secrets, integration channel tokens), encrypted in the same way or with a different key, are re-encrypted with the current installation key when the domain is loaded by the domain center and are saved; sites receive new values by synchronization. The values of a key whose file does not exist and damaged values are not changed (error in the domain center log); Without a given key there is no re-encryption.
-
Mass reissue of integration channel tokens by the administrator: POST /rest/v1/service/integration_points/token (
idsorallwithout service channels, up to 20 channels; roleadmin, only by session), in the admin panel - the “Reissue tokens” action for dedicated channels; new tokens are issued once. -
Report on encrypted domain secrets by encryption method and installation key: GET /rest/v1/domain/crypto_values (role
admin, only by session; in the master domain - for all domains), in the admin panel - section “System” → “Encryption Keys”. -
System status: warnings from the server key service (the installation key file is only in the local copy of the server or is not found) and the domain center (secret values encrypted with a different key by domain; checked when loading and changing objects and when changing the configuration).
-
Configuration secrets (database connection string passwords,
master_admin_pwd, role passwordsmware) are encrypted with the installation key when creating and changing the configuration; When a configuration is activated, its secrets and the secrets of other saved configurations are reencrypted with its key. The password of the private key of thekeypasscertificate of the roles sg, esg, mg, bgmg, ws is now also a configuration secret (previously it was kept open). Values can be entered open. Encryption and keys. -
Installation: the installer creates an installation key on the first server (in
:SYNC/secure/keys/and in the installer directory/var/lib/era/_workdir/erainstaller/secure/keys/); The database password in the initial configuration files is stored encrypted with this key. If key files from a backup copy are placed in the installer directory before installation, a new key is not created: the old one is used (parameterCRYPTOKID, without it - the only or newest file). The server key service copies new keys from:SYNC/secure/keys/to the local server directory, from the installer directory to:SYNC- only the active configuration key (all keys - if there is not a single key file in the available:SYNC/secure/keys/directory); Keys manually removed from:SYNCare not returned. Key files are not overwritten; the damaged file is replaced with a whole copy. psk inlocal.cfg.jsonremains masked, server startup does not depend on key files. -
There is no key file on the server: the nodes are started, the connection to the database with the password of this key is not made and is repeated until the file appears; an error in the log and a warning in the system state. A configuration with a new key, the file of which is not available on some servers, is not activated.
-
Rollback to previous version: previous versions do not decrypt secrets encrypted with the installation key in the database and configurations - rollback only with a database backup made before the update, more details.
-
Backup - database and directory
:SYNC(keys are in it); After creating a new key, make a backup copy of:SYNC. Keys are not automatically deleted; deleting previous keys is an administrator’s decision, more details. Restore - with key files from a backup placed in the installer directory before installation (the key does not change, there is no re-encryption), more details. -
Secret properties of DMS classes (secret property attribute): tokens and secrets of
im/Accountsmessenger accounts, passwordemail/Accounts,client_secretandcertificate_pemofoauth/Providersproviders are stored encrypted with the installation key and read in ciphertext (REST, websocket, subscriptions, scripts, MCP); services decrypt them when used. Changing the secret recipient field (proxy address, mail profile, token URL) by a user without theadminrole requires setting the secret again (422). Re-encrypting a class with the current key - commandreencrypt_secrets(roleadmin), in the admin panel - the “Re-encrypt” button in the class card; unencrypted classes - warning from the domain center in the system state. More. -
Behavior change: scripts, mail and instant messenger strategy scripts, and OAuth login scripts receive account and provider secrets in ciphertext. Open values in the previous changelog and backups remain: if you suspect a leak, change the secrets from the providers. Rollback to the previous version after recording accounts - only with a database backup.
-
Integration channels: when a token is reissued, the channel is disabled and deleted, its HTTP subscriptions (
/api/token/v1/<token>/subscribe,/rest/v1/service/webhooks) are deleted (previously they were valid until the expiration date, up to 24 hours). -
The line with the node cookie was removed from the header of the log files.
-
Help: article Integration channel tokens (where the token is used and how it is protected, TLS requirement); secret parameters are marked uniformly - the appearance when reading and the ability to get the open value (xref: articles: encryption.adoc#secret_mark [more]).
-
Fixed: after restarting the utility service node, events about changes to objects (for example, integration channels) might not be delivered to it until the subscription was renewed.
-
Integration channel tokens: searching for an unknown token does not delay the verification of other requests (previously, a flood of requests with random tokens slowed down the web server); domain tokens of another site are rechecked once a minute, missing tokens - once every 15 seconds; channels of domains created after launch are picked up within an hour without restarting.
-
Websocket API (
rest):hcandsetupoperations for classes with restricted access (x_security) for a user without the admin role -hcreturns a class change mark,setupis disabled (previously the request ended with an internal error). -
The websocket connection identifier passed in the script is signed (with the installation key, if specified); the script can only access connections from its own domain—previously, the identifier could be spoofed.
-
REST and websocket API: check without persistence -
dry_runparameter for creating, replacing, modifying and deleting static collection resources and dynamic model entities. All checks for the record are performed, the response is a resource in the form as after the record, or the same error; nothing is saved. More. -
Domain center: when creating an object based on a model (
ext.copied_from), files are copied only after successful checks; changelicownedis applied only after recording; If a project or other object is deleted unsuccessfully, the change log is not updated. -
Uploading a file via a link (websocket token-API,
file_upload_static): the destination path and file name cannot contain the.and..segments - previously the file could be written outside the specified section. -
Fixed a number of shortcomings in the monitoring API (
/api/monitor/v1: registrations, status, subscriptions, site summaries, domain center) and administration (/api/admin/v1: restart, license, patches, configuration), as well as subscriptions and files by integration channel token: errors are returned as a response instead of an internal server error. -
Improved file API security: file and directory names in request parameters do not extend beyond the allowed directory.
-
Behavior change: subscription to webhooks by channel token (/rest/v1/service/webhooks):
urlfrom the request is applied only if the integration channel does not haveurlset (previously the request’surlhad priority), — as in/api/token/v1/<token>/subscribe. -
BREAKING CHANGE: websocket request dmsquery by default is available only to users and integration channels with the role
admin; the mode is specified by the role parameter ws dmsquery_mode (denied,admin,role- roleadminordmsquery,authorized- previous behavior). -
Configuration check: keys
sip_restore_limit_sec(callstore),ws_ping_interval(sg),mnesia_storage_mode(recmover) are checked by type (previously - a warning about an unknown key);perfmon_tickkey has been deleted. -
System status monitoring (
/api/monitor/v1/system/state): obsolete keysglobal_syncandfsync_roles_not_foundwere removed; a request with them inkeysfails with an error. -
Node processes in the list of processes are located by name: the node line begins with e!<node> (central - E!<node>), its run_erl - with r!<node> (R!<node>); the name is also visible in the cropped output
netstat -p,top; there are two processes per node, including a service one, instead of three. -
Cookie is not transmitted on the command line of node processes, including service ones, and is not written to the log when they are launched. The
local.cfg.jsonfile is accessible only to the user under whom the platform is running; psk is stored in it in a masked form (at the first start after the update, the open value is replaced). -
Fixed: a container running as non-root did not set the limit of open files at startup.
-
Nodes and epmd accept connections only at the address from the node name, if this address is on the server (previously - on all interfaces). Domain name - if it resolves to exactly one server address. Otherwise, as before, on all interfaces; also with the key
dist_listen_any: trueinlocal.cfg.json. Valid after server restart (epmd - after server restart). -
Integration channels of the
mcptype: secret fields of domain center objects (passwords, including SIP accounts, keys, tokens, private keys of certificates) in REST API responses and the change log are given as; filtering and sorting by them is prohibited;sent back does not change the stored value (if the recipient’s address changes, the secret is set again); routes and classes that give away secrets without masking are not available. More. -
Anti-brute force protection: an unknown token (
Authorization: Bearer) on REST API routes with a session is counted as a failed attempt, as an incorrect password (previously it was not counted if the session cookie was not passed). -
Integration channels: option opts.allow_modify (modifications allowed). With
false, the channel token gives read-only access to the REST API,/apiand Websocket Token-API. By defaulttrue- existing integrations work as before. -
Integration channel type
mcp- for MCP agents: user is required, script fields are not allowed, read-only by default; The token is not accepted in direct API requests. -
Behavior change: script component Operation (CRUD in the domain, Search by key) returns the entity in the same way as reading through the API: without service and hidden fields (
t,checksum, hashes); user password - with a mask (without theadminorcrudrole, the script is not issued to the user), the integration channel token - encrypted or a mask with a fingerprint; fields Fields are API names. Scripts that used such fields need to be corrected. -
REST API of domain center collections: collection export (
export=1) outputs all fields as an item export (previously - only default collection fields: the integration channel imported from such an export lost the user and roles). -
REST API
/rest/v1/service/integration_points(collection): fieldstoken_local,token_state,token_remote,token_remote2are issued by default and using the maskmask(previously the collection did not issue them). -
Change behavior: user integration channel token roles - user roles (with group roles) and channel roles under the new opts.roles_mode option:
union(default, union) orintersection(intersection). Same for REST API,/api, model tree, Websocket Token API (subscriptions, rest, dmsbatch), record downloading and MCP. Previously, in REST, channel roles replaced user roles, and in/api, model tree and subscriptions, only user roles were considered. Existing channels receiveunionmode. -
Integration channels: a channel associated with another user (opts.userid) or with roles (
opts.roles) that the user himself does not have, is created, modified (including re-issuing a token) and deleted only by a user with the roleadmin(including through a group); other users - only channels linked to themselves or without a user, with roles from their own (403). -
Integration channel tokens are protected: they are created by the system with a random part and linked to the channel; in clear form are issued once - upon creation and reissue (new operation, session only; closes websocket connections using the previous token); stored encrypted with the installation key (Encryption and keys), searched by hash; when reading, exporting, in the change log and events, they are sent encrypted or masked. More.
-
Behavior change: the integration channel token is not read via the API (only when created and reissued); channel search by token (
LOOKUP,/integration_points/<token>) removed; route/rest/v1/service/integration_tokenshas been deleted. Integrations that received a token by reading a channel should be reconfigured. -
Tokens of the old format (computable) are encrypted when updated and continue to work with the
token_state: legacyattribute (manually entered -invalid) - it is recommended to re-issue; Product layer and meet service channel tokens are reissued automatically. -
Irreversible update. Before upgrading from a version lower than 1.13, save a backup copy of the database and mic working directory: the new version, when launched for the first time, changes the forms of storing secrets in the database and configuration files, rollback is only restored from the copy, data is lost after the update (Rollback after an irreversible upgrade). Check that all tokens are in 32 hex character format (
select code from service.webservices where token_local !~ '^[0-9a-f]{32}$'is empty); a token of a different format does not work after the update (there is a message in the log about an incorrect format), it needs to be reissued. -
Changing the integration channel with a different
token_localvalue (not a mask or the previous one) - error 422, including saving an object read before the token was reissued (the channel stores hashes of previoustoken_revokedtokens: they are not issued in reading, they are issued in export, they are only supplemented at input); the encrypted token is accepted only with thev2binding and only as the token ciphertext (a separate installation key subkey - ciphertexts of other secrets are not suitable); Filtering and sorting by token fields is prohibited. The token mask contains the fingerprint: #<first 8 characters of the SHA-256 token>; when changing,and a mask with a fingerprint of the current token are accepted. Events and change logs carry an encrypted or masked token; Log entries prior to 1.13 may contain public tokens. -
SIP accounts: passwords for additional accounts (
credentials.*.pwd), likepwd, are not issued when read to users without theadminandcrudroles. -
Integration channel of type
im(IM account webhooks): the token is accepted only by the/api/im/v1/<token>webhook, in other interfaces - as unknown; scripts, user, roles and rights not allowed (422); the typeimdoes not change, the other type onimis changed only by the system. When updating, the channel of an account of a different type is converted toim; thewebhookInfo.urladdress is stored with the token and is updated when reissued. To protect against fake webhooks, set provider secrets (vkclient_secret, maxsecret). More. -
Product layer: the public token in microservice teams is replaced by
%TOKEN%; when a token is reissued (including automatically during an update), the microservices are restarted; Re-installation of the product is not required, but restarting microservices is possible. -
Microservices: macro
%TOKENFILE%- path to a file with a token (random name at each launch, rights 0600, the file is deleted 10 seconds after launch and at the end of the process; the microservice should read the file immediately upon startup and delete it); In the logs, the command line is displayed without a token. -
WebConferencing (meet role): the integration channel token is transferred to the WebConferencing server in a one-time file (
era.masterTokenFile), and not on the command line; the file is deleted by the server after reading, as well as 10 seconds after startup and when stopped. -
mcpchannels through the MCP server only reach the REST API (with secret masking) and/apicommands needed by the tools (routing test, call tracing); other paths, including/api/crud, integration channels and their tokens - 403. -
Restart with the
cmdlineparameter (/rest/v1/master/system/jobs,/api/admin/v1/system/restart) and decryption (/rest/v1/master/system/decrypts,/api/admin/v1/pwd/dehash) are available only by session, not by integration channel token. -
Fixed: a request to a web server with a body of unknown length (
Transfer-Encoding: chunked, HTTP/2 withoutContent-Length) when limiting the request rate from the address was enabled, ended with error 500. -
MCP server
/mcp/v1for connecting agents (Claude Code, IDE): authentication with an integration channel token of typemcp, MCP protocol (Streamable HTTP, versions 2025-03-26 - 2025-11-25). Read-only tools: data model (collections, class description, selection with aggregation, entity), domain configuration, routing test, last minute calls, call closures and diagrams (plantuml), search and help reading, stat service indicators dictionary; help and dictionary resources. List of tools - by channel user roles; limiting the frequency and concurrency of calls, cutting down large responses. Preparing and connecting an agent - article Working with the platform through an AI agent (MCP). -
MCP: domain status tools (account and provider registrations, registration errors, ongoing calls, dialing groups, states, scripts, license, conferences), presentation and normalization tests.
-
System status (
role_state): warning if no role instance with virtual addresses in the group is active (addresses are not raised on any server). -
MCP, master domain: system status with a hint for each warning (
system_state), topology and node status; hint to agentsystem_check(report analysis and actions). Help: System State Warnings and Actions. -
Change logs (/rest/v1/journal/changes, class
platform/log/HistoryChanges): change sourcesource–ui(session), token:<channel type> (integration channel token, includingtoken:mcp),script(script),system(platform service). -
Classes: GET /rest/v1/design/classes/metadata - metadata of fields and class options for the editor (types, values, applicability by storage mode).
Dynamic data model
-
Fixed: On a site where the master domain is served through a proxy, the master domain classes after loading did not have their nested properties and access restrictions (x_security) calculated until the classes were first changed.
-
The DMS microservice uses less CPU when idle: schedulers do not keep cores actively waiting.
-
Notifications about data changes: subscriptions with the “property equals value” filter are selected by index, rather than by checking each subscription - with hundreds of subscriptions per class, preparing notifications is tens of times faster.
-
Class processes are created as needed, added when there is a long or large wait for operations in the queue (short bursts of fast operations are not taken into account) and are reduced after a lull without stopping processing (the order of operations on one entity is preserved): idle classes do not hold processes, memory and processes in DMS are smaller (2.3 times fewer processes on the bench). Role parameter class_workers_lazy.
-
Reads from class collections are assigned to the least loaded read process (previously random).
-
In case of short-term unavailability of a class (pause during overload, cleaning, loading), requests wait up to 5 seconds in the order they were received, rather than receiving an error. Resubmissions of requests to the same entity are made in the order of the original submission.
-
Synchronous requests to a class that came during its loading or pause during overload are executed after it in the order of arrival (previously they were lost without a response).
Help Documentation
-
Navigation: the open page is highlighted in the menu, its section is expanded. For pages that are not in the menu, the nearest section is highlighted - previously the menu remained collapsed.
-
Help no longer slows down when opening pages: the search index (10+ MB) is not loaded entirely. The search loads only the parts it needs and only the first time the field is accessed.
-
Search: all query words and their forms are taken into account. Pages with an exact match of the phrase go first, one page - one line, no more than 50 results. The phrase in quotation marks is an exact search.
-
Help pages and resources are transmitted in compressed form (gzip), the traffic is approximately 8 times less.
-
After updating the platform, the browser itself downloads new styles and help scripts; there is no need to clear the cache.
-
Help has been verified with the code: descriptions of configuration parameters, monitoring keys, logs, events and licenses have been corrected; alert events have been restored; Added descriptions of previously undescribed REST API methods; Sections about non-existent functionality have been removed.
-
Same font size in all articles.
Application for working with files
-
The composition includes an application for working with files of platform sections: sounds, certificates, autoprovisioning templates, domain files, published resources and others.
-
Sections are grouped by purpose and provided with explanations: what is stored in them, whether they are synchronized between servers, and whether they are available in the current domain for viewing only.
-
Uploading files and folders, including drag and drop. Replacing, renaming, moving and deleting files.
-
Creating, cleaning and deleting folders in sections with a nested structure.
-
Downloading a folder or section as an archive and loading the archive while maintaining the folder structure.
-
Fixed: downloading a folder as an archive (
DOWNLOADZIP) occasionally returned an empty response; simultaneous downloads on the same server could receive someone else’s archive. -
View images, sound and text without downloading.
-
Copy the file path for scripts, REST API address and public link.
-
Only those actions that are allowed in the section and in the current domain are available.
-
Work on a computer, tablet and phone.
-
Light and dark themes.
-
User Manual for the application.