This is an IBM Automation portal for Cloud Platform 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 updateson 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
We're trying to work with our security teams to create policies that will allow ClearQuest to run at a higher level of permission elevation in our environments. Software on our user's machines is very tightly managed to not allow registry updates or command line calls by default.
The ClearQuest executables we've tested (using v220.127.116.11 on Windows 10):
cqdbsetup.exe (Maintenance Tool) clearquest.exe (both the Win32 client AND the RCP Client)
do not seem to be digitally signed. The Description comes back as either blank or very rudimentary ("clearquest" or "cqdbsetup") and the Publisher comes back as blank (instead of "IBM Rational" or something more meaningful). This is making it difficult for our security teams to make policy exceptions for ClearQuest because of the ease the application could be spoofed without some of this embedded info making it more difficult for a malicious attacker.
We're requesting that in a later version of ClearQuest, IBM takes steps to "sign" their software to make it easier for enterprise business security software to trust elevating their applications.
Do not place IBM confidential, company confidential, or personal information into any field.