Security hardening and IO Manager on phones

platform-2026-10-26
•Platform

Features

  • Users: an administrator can pre-create a single sign-on user for one identity provider.
  • IO Manager: on a phone, tags open level by level with their full names, and a tag opens full-screen with its value, write, publish, rename, alarms and history.

Bug Fixes

  • IO Manager: integrations and connections show on nodes without the HTTP extension installed.
  • Sessions: changing a password, deactivating a user or removing their role ends their open sessions, and a token is valid only for the session it was issued to.
  • Sign-in: an external identity signs in only as the user bound to it, or as a user pre-created for that provider with a verified email.
  • Sign-in: the sign-in rate limit counts the real client address behind trusted proxies, and a locked API key still accepts its correct secret.
  • AI assistant: assistant tools act with the signed-in user's permissions, conversations and approvals belong to their user, approvals show what will run, and replies load no remote content.
  • Programs: programs and rule chains cannot change permissions or roles, every program call runs within a time budget, and one tenant's programs cannot occupy a shared worker.
  • Search: a filtered search matches only on fields the user may read, and expensive filters are bounded.
  • Integrations: a tag cannot write to a permission field or rename a protected entity, and cluster peer addresses are read-only.
  • Configuration: restoring, resetting to a remote or generating a deploy key needs the backup permission, a backup remote must be a network address, and setting the setup remote needs the owner.
  • Extensions: installing an extension from git needs its own permission.
  • Schematics: placement names and button labels are escaped before they are shown.
  • Dependencies: every high and critical advisory in the web interface's dependencies is resolved.