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).
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:
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 an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
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.
Thank you for taking the time to provide your ideas to IBM. We truly value our relationship with you and appreciate your willingness to share details about your experience, your recommendations, and ideas.
Considering the existing workaround options, IBM has evaluated the request and has determined that it cannot be implemented at this time or does not align with our current strategy or roadmap.
In 12 months, you will receive a notification that you can resubmit this request for consideration.
Thank you for bringing your ideas to us. If you have any additional feedback, thoughts or ideas, or if there is anything else I can do, please do not hesitate to reply to this message to continue the conversation.
Ok, thanks for the clarification, it makes much more sense now.
The two current options for the short-term would be:
- use an IdP that can accept multiple different auth sources (like DexIdP https://dexidp.io )
- use our public APIs to remove and configure a new (alternate) IdP in case the primary is down through a script, as API tokens don't rely on the IdP
Meanwhile we're assessing what it would take on our backend to support this and prioritize based on that.
Can you give an example how multiple IdPs are used in any product today?
The purpose of federated authentication is entirely outsourcing the trust to the IdP, which is also why password logins are disabled, since it could lead to conflicts in allowing or denying login access to someone.
Since the purpose of using the tool is to monitor the IdP service itself, I would suggest using an alternative login method entirely.