Page History

The MCP-over-HTTP servers of AI Designer, AI Console and AI Runtime accept connections only from the same computer until an API key is configured.

To connect from another computer, set an API key in the server settings and enter the same key in the client. See MCP and Claude Setup.

The Runtime API accepts a session token only from a Runtime API sign-in or a bearer token linked to a user, and enforces each tag's Read Security and Write Security.

Update custom Runtime API callers to sign in through the Runtime API or use a bearer token linked to a user, and review the security of the tags they read and write.

An AutoStartClient from an earlier release cannot check which redundant server is active on a server of this release.

Install the AutoStartClient from this release on every station that connects to a 10.1.6 server.

Clients on other computers receive blank values for stored passwords and secrets in the configuration tables.

Update any client-side script that read stored passwords or secrets from the configuration tables.

A user who signs in through an external identity provider and matches a user in the solution receives that user's permission groups, and the provider's group claims are ignored.

Review the permission groups of solution users who sign in through an external identity provider.

On clients connected with Windows authentication, electronic signatures and alarm acknowledgment comments check the Windows password of the user named, in the server's own domain only.

Have operators sign with their Windows password, and use accounts from the server's domain.

File and process services between FrameworX computers accept only allowed folders and FrameworX programs.

Add each folder used for remote solution loading or file transfer to the allowed folders in the machine settings, and restart the service.

On Windows, the runtime reads start settings and .NET 10 database provider registrations only from the installation folder, and a start settings file is selected by solution and profile.

Move start settings and custom provider registrations from the shared settings folder to the installation folder, and place them again after installing a new release.

Dataset filters and queries refuse to run when a value from a tag or from the signed-in user would end a quoted text in the SQL command.

Test Dataset queries and table filters after upgrading, and where a value closes the quotes on purpose, move the quotes from the query into the value.

A Linux or Docker runtime refuses to start a solution that targets Windows.

Open the solution in the Designer, change the target platform to Multiplatform in Solution Settings and run Build All.

Client stations receive tag values from the server after a reconnection or an online configuration change.

Update every Smart Client and Rich Client, local and remote, to this release.