Cloud Management and AIOps
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).
Shape the future of IBM!
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:
Search existing ideas
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 your ideas
Post an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
Specific links you will want to bookmark for future use
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.
The functionality described in the above comment meets the needs of the requestor.
After a sync up with engineering, we've got a way forward on this idea that is within reach for delivery.
The proposed solution is the addition of a new authentication schema and action block to the Common integration. IMPORTANT: This would mark the first and only place in the product where an authKey's contents could become visible to the user in the debugger, the core dump, or the flow output.
The authentication schema would have a single field, and the field could take any type of data: a number, a string, a boolean, an object, or an array. The data stored within is completely up to the user. The input field will have a clear warning in the description that the data placed inside will be accessible to whatever user has access. There would be a small size limit.
The related "Get Config Data" block would be able to use ONLY the authentication type above, and would return the contents as its result output property. This would enable the use of the value(s) within via variable constructions like these:
$Get_Config_Data_1.result (value of a simple type)
$Get_Config_Data_1.result.my_value (value of a property of an object)
$Get_Config_Data_1.result[3] (value of an array element by index)
The best way to meet this need is to create a native Pliant integration with the target system, which moves the authentication securely into its own authentication schema. These integrations can be created in <15 business days. Does that meet the need here? @Guest @Guest