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.

September 2026 Upgrade (version nevisid-9.2609.0)​

Swiss e-ID (swiyu) Login​

This release advances the Swiss e-ID (swiyu) login integration. The SwissEID verifier component has been upgraded from 2.1.2 to 4.2.0, and the swiyu login flow now validates credentials against the official Swiss federal trust infrastructure (accepted issuer DIDs on the swiyu trust registry).

What this means for you:

  • Users can authenticate with their Swiss e-ID (swiyu) wallet through a QR-code login step.
  • The integration is aligned with the current swiyu verifier release and issuer set.

nevisIDM Prune History Job​

A new Prune History Job is now available for nevisIDM and included in the example project. It periodically prunes historical records, helping keep the identity database compact and performant over time.

Role-Based Access to the Management Console​

Administrators can now be given different levels of access to the Nevis ID Console. What each administrator can see and do is determined by the role(s) assigned to them for the Nevis ID instance, so you can grant each person exactly the access their tasks require instead of full access for everyone.

Three roles are available. A user can hold more than one at the same time — the access is combined:

  • Business — access to the Dashboards (read-only analytics). User management, terms & conditions, and all configuration and integration areas are not available.
  • Support — everything in Business, plus user management and terms & conditions. Advanced settings, configuration, federation, and logs are not available.
  • Integrator — full, unrestricted access to the Management Console.

Restricted areas are not hidden — they stay visible in the menu but are shown greyed out, so administrators can always see the full scope of the product and which capabilities a higher role would unlock.

What this means for you:

  • By default, every administrator keeps the Integrator role and therefore the same full access to the Management Console as before. Access is only narrowed for a user when this is specifically requested — nothing is removed automatically.
  • If you are a partner administrator with the User Management role on the Nevis Portal, you can manage these roles yourself: log in to the Portal (portal.nevis.net), go to User management, open the target user, and under Access Rights toggle the desired role(s) on or off, then save.
  • Role changes take effect at the user's next login. If a user still sees their previous access, they should log out and clear their browser session (or wait for the existing session to expire), then log in again.
  • If you don't have a partner administrator with the User Management role, role changes can be requested through Nevis customer support portal.

Fixes & Improvements​

  • Password lockout handling — resolved issues affecting password lockout behavior.
  • Mobile authentication — fixes across the mobile auth use case.
  • Threat Intelligence — risk-score data plumbing between nevisAdapt and the Console has been extended.

Security​

TLS 1.3 enforced on all hostnames — all Nevis ID hostnames now negotiate TLS 1.3 only. ⚠️ Client-compatibility impact: clients that cannot negotiate TLS 1.3 (very old browsers / TLS libraries) will no longer connect.

SwissEID verifier upgraded to 4.2.0 — brings the swiyu verifier up two major versions, including upstream security fixes.

Action Required — TLS 1.3 Now Required​

As part of ongoing security hardening, all Nevis ID hostnames now require TLS 1.3 as the minimum protocol version. Connections that can only negotiate TLS 1.2 or lower will be rejected.

Who may be affected:

  • End users on very old browsers (pre-2019). TLS 1.3 is supported by Chrome/Edge, Firefox, and Safari releases from 2018–2019 onward, so up-to-date browsers are unaffected.

  • Server-to-server / API integrations built on older TLS stacks — for example OpenSSL earlier than 1.1.1, Java 8 before update 261, or legacy .NET Framework configurations.

  • Embedded, IoT, or kiosk clients with outdated TLS libraries.

    What you should do:

  • Confirm that any application, script, or service integrating with your Nevis ID instance can negotiate TLS 1.3.

  • Update the underlying TLS library / runtime where needed (modern OpenSSL, Java 11+, current .NET).

  • If you operate managed or kiosk devices, verify their browsers/OS support TLS 1.3.

No action is required for end users on current mainstream browsers and operating systems — they already negotiate TLS 1.3 automatically. For questions about this release, please contact your Nevis support representative or visit docs.nevis.net.

August 2026 Upgrade (release/nevisid-9.2608.0)​

Nevis manages Deployment Target​

The setting Deployment Target in instance patterns is now managed by Nevis. This is part of our continuous effort to hide infrastructure level aspects.

You do not have to enter any value. When you deploy your project, the service will be established using the correct infrastructure configurations managed by Nevis.

Introducing User pages​

We are introducing the new User pages to the Nevis ID Console! This release brings a redesigned experience for browsing and managing users within your identity environment. This includes:

  • Users list view — Browse users in a paginated table with quick access to key details such as name, email, and last login.
  • User details page — Open any user to view their information across a tabbed layout:
    • General information — Core user attributes at a glance.
    • Profiles — View the user's profiles, application roles, and system role assignments.
  • Credentials tab — Viewing password, FIDO2, certificate, OAUTH and other credentials.
  • User actions — Blocking / unblocking users (with confirmation).

Notification System (Service Status & Announcements)​

We're introducing a notification system to the Nevis ID Console, keeping you informed about service status, incidents, maintenance, and announcements. It's powered by StatusPal, pulling live updates from the Nevis status page. It includes:

  • Status banner — The latest status update is visible on top of the page, with the ability to dismiss it once read.
  • Notification bell — A bell icon in the header surfaces all active notifications, with an unread count badge. Click the bell to see your notifications, with:
    • Read / unread tracking — Unread items are highlighted with a dot; click a notice to expand its details and mark it as read.
    • Mark all as read — Clear your unread notifications in one click.
    • Show all / Show less — Focus on unread items by default, or expand to see everything.
    • A "Go to status page" link for the full picture at status.nevis.net.
    • Unread Marker in Title — unread messages are marked with (n) in title as well to see at a glance whether you have a new unread notification.

Nevis ID Release Selection​

You can now configure your instance against a validated release rather than picking component and pattern versions independently.

A release bundles a tested, compatible combination of:

  • Nevis component versions (the Docker image versions of nevisAuth, nevisIDM, nevisAdmin4, and the other components)
  • Pattern versions (the nevisAdmin4 pattern versions)

Selecting a release in the Nevis ID Console applies that whole combination at once, so you no longer have to match versions by hand or risk an incompatible setup.

Integration Intelligence (Configuration building and Troubleshooting)​

We're upgrading Nevis ID Integration Intelligence with two new features:

  • Configuration building: receive step-by-step help and pattern creation for three authentication flow use cases. After assessing the open project, it suggests patterns and resources to create. Click the Tool icon in the chat window.

  • Troubleshooting helper: get suggestions and help for the deployed project. It reads logs, configuration, and variables to resolve issues. Click the Warning icon in the chat window.

note

No security patches are included in this release.

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