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.
@Guest
You can create synthetic credentials for username and password by using the he Instana Open API. Then you can use them in the script, by using the global variable $secure provided by Instana api. Here an example on how to use it in a script recorded with selenium IDE.
Máté Návay
We are using Seleium IDE to record the Synthetic monitoring rather than using Java or nodeJS
Can you share more details/references in your reply?
Also, From IBM URL, is asking us to purchase another product to secure passwords in Synthetic monitoring Browser script rather than it is a native feature coming from Instana .....
Credentials for tests should be stored separately using the credentials feature, where there is already individual permissions to be able to use credentials and configure them.
Tests' access can already be defined on an individual level, but further controls are in development to specifiy which credentials a group can have access to which is evaluated at script execution.
Should a user try to include credentials they don't have access to, these will not be injected into the script.