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.
In IBM App Connect Enterprise 12.0.9.0 and above (more details here: https://community.ibm.com/community/user/integration/blogs/ben-thompson1/2023/07/04/ace-12-0-9-0), there is a feature which allows a user's Java code (running inside a JavaCompute node in a deployed message flow) to query and gain access to credentials which are known to the integration server due to being stored in its vault. This is potentially useful for users who wish to use credentials within their own bespoke logic running in Java, and who want to exploit the convenience of having ACE store the credential safely on their behalf. The getCredential method can be used like this:
myCred = MbCredential.getCredential(“ODBC”, “myDSN”);
By default, this feature only allows access to credentials which are of the user-defined type. This aspect of behaviour can be controlled by a setting in the server.conf.yaml file. The stanza shown below can be editted so that if you want to extend access to also include other credential types then you may do so:
Credentials:
#userRetrievableCredentialTypes: 'userdefined' # Sets the comma separated list of credential types that user code is allowed to reference. Default is 'userdefined'.
# The list can be empty to disallow credential lookups from user code.
# Set the value to 'ALL' to allow access to credentials of any type from user code.
The context of this idea appears to be the public cloud variant of ACE (App Connect Enterprise as a Service on AWS). This service has the relevant versions of ACE available. Status of the idea is updated to Delivered.