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.
See this idea on ideas.ibm.com
We can only execute APIs using a local user or Oauth. So, we have 2 problems: a) local user can't be protected like an SSO user (like when using Azure AD for conditional access); b) Oauth authentication in Turbo for APIs makes the Turbonomic an Oauth provider when it should use SSO (Azure AD in my customer scenario) as the provider. In the same way as a local user using Oauth for API calls, I cannot control where somebody will use those credentials.
The suggestions is to be able to call APIs using SAML/SSO credential/token.
Idea priority | Urgent |
By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.
We truly value our relationship with you and appreciate your willingness to share details about your experiences and ideas. We think this is a good idea and will target it for inclusion in a future release.
Thank you for taking time to meet with us to discuss the details of this idea. We will be working on designing an approach that satisfies the requirements that were provided.
If we create a dedicated instance for Itau, can we restrict the IP range that can access the APIs?
Hi team, is possible to restrict the source IP that will call APIs in the Itau tenant using a filter on WAF?