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.
Even if we create another local user account, it will have the same problem as admin user. When DP is configured to use RADIUS, we use 2-factor authentication (with an RSA token) to login to datapower, This won't work with SOMA scripts as the RSA token changes every 30 seconds and cannot be used.
The ideal solution is to have an option to provide a list of local user ids to bypass the RBM primary authentication and authorization and go straight to local user authentication and authorization. This will not break the current RBM logics and ensure the backward compatibility.
What about just avoiding to use the builtin admin user? IMHO there are very rare cases where you really have to use the admin user.