Skip to Main Content
Cloud and AIOps


This is an IBM Automation portal for Cloud Management, Technology Cost Management, Network Automation and AIOps products. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).

Shape the future of IBM!

We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:

Search existing ideas

Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,

Post your ideas
  1. Post an idea.

  2. Get feedback from the IBM team and other customers to refine your idea.

  3. Follow the idea through the IBM Ideas process.

Specific links you will want to bookmark for future use

Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.

ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

Status Future consideration
Workspace SevOne
Created by Guest
Created on Mar 2, 2026

Make SevOne SSO fully resilient so authentication continues to work automatically during leader failover without manual reconfiguration

SevOne removed support for RADIUS/TACACS in recent versions, leaving LDAP (resilient but weak/single‑factor) and SSO (strong but not resilient).
Currently, SevOne SSO breaks during cluster leader failover and requires manual reconfiguration of both SevOne and the Identity Provider.
This prevents us in Euroclear from using strong authentication and forces us to rely on a temporary security exception.

Why is it useful? Who benefits? How should it work?

A resilient SSO mechanism would allow SevOne to maintain MFA‑based authentication across all failover scenarios.
All SevOne customers using HA clusters would benefit.

How it should work:

  • SSO should continue working automatically across leader failover.
  • No manual updates to SevOne SSO config or the Identity Provider should be needed.
  • SSO configuration should replicate across all peers.

This enables compliant strong authentication without service interruption.

Idea priority High
  • Admin
    Ryan Wilson
    Sep 30, 2026

    Khaoula,

    Thanks for following up on this. We released NMS 8.2 with Dex removed and recommend that customers use Keycloak (when needed) to setup SSO. Keycloak has the ability to configure multiple redirect IPs and my development team believe that it should be possible for this configuration to support cluster leader failover, and possibly using a non-cluster-leader as the redirect IP. I've asked my engineers to open a QA Test ticket to validate and, if it works, to add public documentation updates. Please feel free to contact me directly if you don't hear back within a week - ryan.wilson4@ibm.com

    Regards

  • Guest
    Sep 30, 2026

    Hello Ryan,

    We recently upgraded our SevOne cluster to NMS 8.2.2 and I wanted to check whether there have been any updates regarding the Keycloak setup with alternate redirect IPs that you mentioned previously.

    Our main concern is that SSO is currently not disaster-recovery compliant because authentication depends on the cluster leader. If the leader fails, manual reconfiguration is required before users can authenticate again.

    SSO should continue to function seamlessly during a leader failover without requiring any manual changes on either the Identity Provider or the SevOne side. The authentication service should remain fully operational across the cluster, even after a failover.

    As this remains the main blocker preventing us from adopting SSO, any update on the Keycloak investigation would be greatly appreciated.

    Kind Regards,


    Khaoula KARAM

    Euroclear

  • Admin
    Ryan Wilson
    Mar 4, 2026

    Khaoula,

    Currently SSO with SevOne is setup using an instance of Dex that runs on the cluster leader. In NMS 8.2 we are deleting Dex for security reasons and requiring customers to migrate to another solution, with IBM recommending Keycloak. We are currently testing whether Keycloak can be setup with alternate redirect IPs for the IdP to function if the cluster leader fails over or even goes down by redirecting the responsibility to authenticate via one of the other peers.

    While we work on this I'd appreciate if you have any thoughts or feedback on this potential approach.

    Regards,

    Ryan Wilson, Senior Product Manager, SevOne NPM