Skip to Main Content
Cloud Management and AIOps

This is an IBM Automation portal for Cloud Management 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 (

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 ( - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal ( - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM. - 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 Apr 26, 2024

SAML Login to disabled account

With users disabled on NMS it forces MFA/SSO which works currently.  However, the customer found out while deploying DI that DI fails with users disabled on the NMS.

Idea priority Urgent
  • Admin
    Ryan Wilson
    Apr 26, 2024

    @Guest - is the ask here when using SSO/SAML based accounts, and one of those accounts is locked out that they be able to backdoor the account with local auth or something? It's really not clear what the issue and ask is.

    Can you clarify what it means for "DI to fail" if a user is disabled? Can nobody login at all? If not, why is it a problem that one user is disabled? Shouldn't that user have their account re-enabled upstream in the SSO auth workflow?