Skip to main content

Changelog

Nevis is updating Nevis ID frequently to roll out new features and to ensure you have the best possible experience.

We will reach out to you when changes to your project are required.

July 2026 Upgrade​

Simplified Configuration Management: Inventory Hidden, Variables Editable Directly​

To provide a more reliable and streamlined experience, we have updated how configuration is handled. Nevis now takes care of all infrastructure and operational management for the Nevis ID SaaS platform. Therefore, the raw inventory editor has been removed from the default integrator view. This ensures a safer configuration environment by protecting core infrastructure settings.

In its place, configuration variable values can now be viewed and edited directly on the Variables screen. All inventories you have access to are listed there, and changes are saved automatically to the correct inventory.

What this means for you:

  • Integrators no longer have access to the underlying inventory editor. Infrastructure settings remain under Nevis control.
  • Variable values can be updated from the Variables screen, without editing the inventory directly.
  • Secret references can still be created and managed. For new secrets, use the Secrets & Files screen going forward.
  • All existing configurations continue to work without any changes required on your side.
note

This feature is specific to Nevis ID and is not available in on-premises deployments. If you have any questions about how this affects your configuration workflow, please do not hesitate to reach out to your Nevis contact.

Automatic Database Name​

The setting Database Name in database patterns can now be left empty. In that case, the pattern calculates the database name based on the component name and the namespace/name of the inventory.

The expected format is <component>_<namespace>, for example nevisproxy_live or nevisauth_test.

If you already use the expected database name, you can clear this setting. Using an inventory variable is also supported, as long as that variable contains the expected value.

If the configured value differs, a warning is shown in the deployment preview. The warning explains that Nevis cannot currently rule out database sharing across environments, which is dangerous. If you are affected, contact Nevis support.

Improved Session Reliability​

We have optimized session handling to ensure a consistently reliable user experience. This update addresses rare scenarios where unexpected "session-expired" or 400: CSRF check failed popups could appear. Multi-step login sequences, such as entering a password followed by an OTP, have also been strengthened to ensure a flawless authentication flow.

Requests to your Nevis ID environment were previously subject to a 15-second default timeout at the gateway layer. This has been raised to 60 seconds, reducing the chance that a slower authentication step is cut off prematurely. This can include, for example, an OTP or MFA verification that takes a little longer.

Known limitation: nevisIDM QueryService is not supported in High Availability mode​

The nevisIDM QueryService API is not available in High Availability (multi-pod) deployments and remains disabled by default. If you require QueryService, contact Nevis to discuss supported options.

Other improvements and fixes​

  • Nevis ID Data Model — documentation of the Nevis ID clients in nevisIDM is now available on docs.nevis.net. It includes client names and IDs and their intended use.
  • Copilot requests from the Nevis ID management console now include additional context, improving tool-call reliability.
  • Fixed a 404 error on the Terms & Conditions page (/languages).
  • Fixed an issue where Copilot lost the ability to call tools after logging in to the Unified User Interface (UUI) via SSO.
note

No security patches are included in this release.

May 2026 Upgrade​

Manage Kubernetes Secrets​

The Secrets & Files screen now includes a Kubernetes Secrets section where you can create and manage Kubernetes secrets directly from the management console.

Previously, you had to share sensitive values with Nevis support for secrets to be created in your cluster on your behalf. With this feature, you can create secrets yourself without exposing sensitive values to any third party.

The section displays the Kubernetes secrets in the namespace of the selected inventory. Secrets provisioned externally — for example, secrets set up by Nevis as part of your instance — are visible with a read-only indicator so you can copy their references into your inventory variables. Secret values are never shown on screen.

For details, see Manage Secrets.

Service Name Alignment​

To prepare for future improvements for the Infrastructure section in the management console, the name of services in the inventory have to be aligned. Nevis will assist you with this change. Please ensure you use only the following names:

  • proxy
  • auth
  • login - for nevisLogrend
  • idm
  • meta
  • fidouaf
  • fido2
  • adapt