Observability

Edit Custom Properties from Manage Nodes logs user out / kicks user to login page for SolarWinds Platform 2026.1 and 2026.1.1

This article provides information about an issue in SolarWinds Platform 2026.1 and 2026.1.1 where using the Custom Properties Editor action from the legacy Manage Nodes page can intermittently log the user out and redirect to the login page instead of opening the custom properties editor.

First published date

2/24/2026 8:21 AM

Last published date

6/15/2026 3:49 PM

Overview

After upgrading to SolarWinds Platform 2026.1 or 2026.1.1 and the user performs the following steps:

  1. Opens the legacy Manage Nodes page.
  2. Selects one or more nodes.
  3. Clicks the Custom Properties Editor button.

The browser does not reliably stay on the Edit Custom Properties page. Instead, soon after the editor attempts to load, the user is redirected back to the SolarWinds login page with a session timeout indication.

Example of similar log evidence:

In ApolloWebApi.log, you may see a sequence similar to:

DEBUG ... BeginRequest (GET ...): https://<orion-server>/api2/custom-properties/get-default-columns-for-cp-editor?EntityName=Orion.Nodes
DEBUG ... SessionManagerEngine - VALIDATION: Session '<session-id>' is active and owned by '<account>'. Valid.
DEBUG ... EndRequest (GET ...): https://<orion-server>/api2/custom-properties/get-default-columns-for-cp-editor?EntityName=Orion.Nodes

Shortly afterward (typically within 10–30 seconds), the session disappears from the WebSessions table:

DEBUG SessionManagerEngine - SYNCHRONIZATION: Started.
DEBUG SessionManagerEngine - Synchronizing LastSeen status for <n> session(s).
DEBUG SqlHelper - UPDATE [dbo].[WebSessions] SET [LastSeen] = @lastSeen
  WHERE [SessionID] = @sessionId (sessionId=<session-id>, lastSeen=<timestamp>)
DEBUG SessionManagerEngine - Session '<session-id>' is no longer in DB. Removing from local cache.
DEBUG SessionManagerEngine - Reloading web sessions cache from DB.

There is no corresponding /api2/logout request, and no obvious authentication/XSRF error for that session in the same time window, which makes it appear to the user that simply clicking Custom Properties Editor caused a forced logout.

Symptoms:

  • When you click Manage Nodes → Custom Properties Editor, you are immediately returned to the login page instead of seeing the editor.
  • The page appears to instantly time out, and you are kicked back to the login screen.
  • You see a “session timed out” or similar session-timeout message after clicking Custom Properties Editor.
  • Custom Property Editor never opens; only the login page is displayed.
  • Attempting to edit custom properties from the Manage Nodes view causes you to be logged out of the web console.

Product section

Hybrid Cloud Observability

Cause

This behavior has been identified as a known product issue in SolarWinds Platform 2026.1 and 2026.1.1 that affects the legacy Manage Nodes → Custom Properties Editor navigation path. In certain cases, using this specific path can cause the user’s web session to be treated as expired and redirect to the login page instead of opening the editor.

Other supported navigation paths for managing custom properties (such as Settings → All Settings → Manage Custom Properties → View/Edit Values) continue to function as expected.

Resolution

To resolve this issue, please upgrade to SolarWinds Platform 2026.2. If an upgrade is not possible, perform the following steps:

 

Workaround 1 – Use Manage Custom Properties directly (recommended for customers)

Instead of using the Custom Properties Editor button in the legacy Manage Nodes view:

  • In the web console, go to:
    Settings → All Settings → Manage Custom Properties.

This path uses the modern Manage Custom Properties experience and does not exhibit the logout behavior.

Workaround 2 – Use node‑level Edit Properties / Edit Node (where applicable)

For smaller‑scale changes, you can:

  1. Navigate to the individual node’s details page.
  2. Use Edit Properties / Edit Node to modify relevant system and custom properties.
  3. Save changes.

This avoids the problematic Manage Nodes → Custom Properties Editor link, though it is less efficient for bulk updates.