Skip to main content
Back

Onyx Cuts First-Token Latency 6x and Locks Down Enterprise Auth

Onyx v4.5.0 lands with SSO-only login, per-chat reasoning controls, a Box connector, native Azure Blob storage, and big latency wins.

Pro

Repo, Full Access
  • Onyx v4.5.0 released with SSO-only login, disabling password auth entirely for deployments that require it.
  • Chat gains per-session reasoning-effort and temperature sliders, plus a context-window gauge on the model selector.
  • New Box connector with permission sync mirrors collaborations and shared links into document ACLs.
  • Native Azure Blob Storage file store backend removes the need for MinIO or S3 proxies in Azure deployments.
  • First-token latency for concurrent chats dropped from ~354ms to ~54ms via new database indexes.
  • Breaking defaults: debug tools removed from backend image, Helm 0.8.x retuning, AWS Terraform t-shirt sizing, UTC-day rate limits.

The team behind Onyx, the open-source AI chat and enterprise search platform formerly known as Danswer, has shipped v4.5.0. It is a maintenance-heavy release that continues the platform's push into hardened, enterprise-ready deployments, with a handful of user-facing controls that finally give people knobs over reasoning effort and temperature on a per-conversation basis.

The headline changes cluster around three themes: locking down authentication, giving chat users finer control over model behavior, and cleaning up the deployment story for teams running Onyx on Kubernetes, AWS, or pure-Azure stacks. The changelog also flags several breaking-ish default changes that operators should read before upgrading.

SSO-only login and identity provider fixes

This is one of the platform's largest releases to date, and it includes a completely rebuilt chat experience, the Onyx Desktop App and MCP Server, and smarter model management layered on top of the auth changes. Password authentication can now be switched off entirely for deployments that want to force SSO. A new toggle under Security Hardening removes the email/password form and signup links from the login page while SSO login and provisioning continue, with lockout guards that require an enabled SSO provider and prevent disabling the last one while password auth is off.

OIDC also gets a real production polish. It now works out of the box with Microsoft Entra ID (a missing email_verified claim is tolerated behind a per-provider strict opt-in) and Amazon Cognito, where