Skip to content

TensorPM v1.21.1

Choose a tag to compare

@Neo552 Neo552 released this 13 Jul 16:05
· 73 commits to main since this release

Changelog - v1.21.1

TensorPM 1.21.1 improves connectivity in managed enterprise networks and adds secure,
optional authentication for local or self-hosted AI endpoints.

πŸŽ‰ New Features

Enterprise certificate support

TensorPM backend connections now honor trusted enterprise root certificates installed by the
operating system, including certificates used for TLS inspection and company-internal PKI.

  • Corporate root certificates installed on Windows or macOS are recognized by TensorPM.
  • HTTPS inspection environments, including deployments using Zscaler, can connect without
    disabling certificate validation.
  • Windows trusts certificates from both the current-user and local-machine root stores while
    continuing to reject certificates placed in the Windows Disallowed stores.
  • Public certificate authorities and explicitly configured additional certificates remain
    available, preserving existing connectivity.
  • Support packages report certificate trust sources and counts without exporting certificate
    contents.

Optional API keys for local AI endpoints

Local and self-hosted OpenAI-compatible endpoints can now be configured with just a URL, model,
and optional API key. No provider selection is required.

  • API keys are sent as Bearer authentication to the configured endpoint.
  • Keys are encrypted with the operating system's secure credential storage and are never displayed
    again after saving.
  • Each key is bound to its endpoint and can be replaced or removed from Settings.
  • API keys are allowed over HTTPS and over HTTP only for loopback addresses such as localhost.
  • Existing Ollama and other no-key configurations continue to work without changes.

πŸ”’ Security Improvements

  • API keys are encrypted using operating-system-backed secure storage and bound to their configured
    endpoint.
  • Stored keys are never returned to the interface after saving.
  • Credentials are sent only over HTTPS, with HTTP permitted only for loopback addresses such as
    localhost.
  • TensorPM refuses to persist a key when secure operating-system encryption is unavailable.
  • Windows certificates that are explicitly distrusted remain rejected.
  • Explicit per-request certificate policies remain restrictive and are not widened by the new
    operating-system trust integration.
  • Support packages now redact a wider range of API-key, authorization, token, password, and
    credential formats.

πŸ“ Notes

  • Install the company or Zscaler root certificate as a trusted operating-system root and restart
    TensorPM after adding, removing, trusting, or distrusting it.
  • The enterprise certificate support covers server trust and HTTPS inspection. Client certificates
    and mutual TLS are not introduced in this release.
  • No database migration or configuration change is required for existing users.

πŸ“… Release Info

  • Version: 1.21.1
  • Release Date: July 13, 2026
  • Previous Version: 1.21.0
  • Type: Patch Release