This is an IBM Automation portal for Integration 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
API Connect Dev Portal currently supports only OIDC based two factor authentication. We are looking for two factor authentication support using Mobile OTP/Email OTP/Authenticator App
Idea priority | High |
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 will never implement 2FA on the local user registry in API Connect. For production use cases, we strongly recommend using a commercial third-party identity provider that conforms with the federated identity protocols (e.g. OIDC) that API Connect supports.
Hi Dan,
For Mobile OTP, customer is fine if we provide option if we can use their hosted API and they can provide integration to their SMS Gateway provider.
I will get more specific requirements for Authenticator
Thank you for the idea, for IBM to proceed with the request it does require additional specific requirements and business case justifications. Without additional details this request will be closed within 30 days.
As part of the specific requirements:
Mobile OTP - What integration point(s) is the client looking for e.g Twillio Verify for 2FA as API Connect would need to partner with a SMS solution. Or would API Connect send to an client hosted API and the client be required to provide the integration to the SMS Gateway provider.
Authenticator App - Please be more specific if this to support FIDO2 Authenticators (CTAPS + WebAuthn) or RFC 6238 Time-based One-Time Passwords (TOTP), or Radius MFA, or other solution.