Neeve Release Notes

Prev Next

1. Introduction

This document provides information on the features, improvements, and known issues for this Neeve release. The Neeve Portal is currently in Beta stage. It may be missing features or have small bugs. We are targeting monthly releases to continue improving the product experience and adding new functionality. Read on to learn more about what’s included in the latest release.

2. Changes in this release (Neeve Portal v1.4.5)

This release is only for our multi-tenant architecture. Not all portals will be upgraded to this release at this time.

2.1 New Features

Single Sign-On (SSO) – SAML Support

  • Full SAML-based SSO configuration via UI

  • Create, edit, and manage SSO providers directly in the portal

  • Identity Provider (IdP) configuration view with key metadata (Entity ID, SSO URL, certificates)

  • Home Realm Discovery (HRD) support for domain-based login routing

  • SSO enforcement controls (force users to authenticate via SSO)

  • Enable/disable SSO connections dynamically

SSO User Experience Improvements

  • Domain-based user invitation flow aligns users to correct IdP

  • Improved lifecycle handling for SSO connections (create, update, delete)

2.2 Enhancements

User Management & Organization Experience

  • Consistent use of Organization Display Name across UI, emails, and system surfaces

  • Improved user lifecycle handling (disable, delete, restore flows)

  • Better handling of multi-org user attribution (e.g., “Created By” accuracy)

UI / Design System (DLS) Improvements

  • Migration from “Card” to “Tile” components for consistency

  • Improved visual consistency across portal pages

  • Introduction of reusable Accordion component

  • Favicon now reflects organization display name initials

  • General UI cleanup and consistency improvements across components

Table & Form Behavior

  • Improved validation behavior (e.g., removal of unnecessary mandatory fields)

  • Cleaner handling of bulk actions and table interactions

Performance & Backend Improvements

  • Per-request timeout controls for better API reliability

  • Redis performance improvements (replacing blocking operations with scalable patterns)

  • Improved handling of high-volume operations and large datasets

Developer & CI/CD Improvements

  • Automated DLS updates and versioning strategy

  • Improved deployment automation across control plane and data plane

  • Enhanced developer tooling and validation checks

Eventing & Data Pipeline Foundations

  • Introduction of event-driven architecture components:

    • JetStream-based event publishing

    • Publisher pipeline with retry and recovery mechanisms

    • Projector service scaffolding

  • Metrics instrumentation for event pipelines (rate, lag, errors)

  • Idempotency and event deduplication logic

  • Startup recovery (“catch-up”) for missed events

2.3 Bug Fixes

User & Access Management

  • Fixed issue where user disable action could fail

  • Fixed deleted users incorrectly remaining in “Active” state

  • Fixed incorrect “Created By” attribution across organizations

  • Fixed issues with user deletion and restoration flows

UI / Portal Issues

  • Fixed Delete button not functioning in configuration screens

  • Fixed welcome email sender displaying incorrectly (“no-reply” issue)

  • Fixed UI inconsistencies in SSO configuration views

Migration & Networking

  • Fixed multiple errors during CloudBrink migration steps (400/500 errors)

  • Fixed missing WAN network visibility after migration

  • Fixed issues with service port mismatches in network views

Logs & Audit

  • Improved migration completeness for audit and access logs

  • Addressed inconsistencies in log data after migration

3. Prerequisites

3.1 Cloud Requirements

The following cloud platforms are supported:

  • Amazon AWS

  • Microsoft Azure

  • VMware vSphere v6.x

  • Google Cloud

3.1.1 Cloud Connector Compute Requirements

  • 2 vCPU

  • 2GB RAM

  • 10GB HDD

  • Public IP address

4. Issues

4.1 Known Limitations

The following limitations exist within the Neeve portal. Due to the beta nature of the Neeve Portal, not all features are available.

  • Refer to internal documentation for a comprehensive list of limitations.

  • Cloud BMS-enabled portals cannot be deactivated.

  • Privilege escalation does not trigger email notifications.

  • UI does not auto-refresh after configuration changes.

  • Bulk onboarding toast messages may overwhelm the UI.

  • Multi-org logout must be handled manually.

  • User hierarchy visibility limitations across orgs/sites/portfolios.

  • Launcher favorites reorder behavior may appear inconsistent.

  • Secure Edge and Neeve Portal configuration conflicts may overwrite changes.

  • Some onboarding diagrams do not reflect all hardware form factors.

  • CSV export is limited to 1000 entries.