Cloud Platform

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:

Post your ideas

Start by posting ideas and requests to enhance a product or service. Take a look at ideas others have posted and upvote them if they matter to you,

  1. Post an idea

  2. Upvote ideas that matter most to you

  3. Get feedback from the IBM team to refine your idea

Help IBM prioritize your ideas and requests

The IBM team may need your help to refine the ideas so they may ask for more information or feedback. The offering manager team will then decide if they can begin working on your idea. If they can start during the next development cycle, they will put the idea on the priority list. Each team at IBM works on a different schedule, where some ideas can be implemented right away, others may be placed on a different schedule.

Receive a notification on the decision

Some ideas can be implemented at IBM, while others may not fit within the development plans for the product. In either case, the team will let you know as soon as possible. In some cases, we may be able to find alternatives for ideas which cannot be implemented in a reasonable time.

If you encounter any issues accessing the Ideas portals, please send email describing the issue to ideasibm@us.ibm.com for resolution.

For more information about IBM's Ideas program visit ibm.com/ideas.

Status Future consideration
Categories ClearQuest
Created by Guest
Created on Dec 15, 2017

Provide file-based ClearQuest connection support on Windows (similar to on Linux/UNIX)

The federal government has been implementing DFARS (NIST 800-171) requirements for a few years. These are mandatory and effective as of December 31, 2017.

One of the DFARS requirements is that database usernames are changed every 90 days. This wreaks havoc on ClearQuest connections, especially on Windows. Changing the registry-based connection information for all users in a multi-thousand user environment is a huge overhead... especially every 90 days. In addition to the problem of changing the registry-based connection information, if a user somehow does not receive the update, a few unsuccessful attempts to login will lock the ClearQuest user database for all users.

Please make a file-based connection available to Windows clients, similar to the file-based connection method used on Linux/UNIX clients. This would allow Windows desktop clients to reference a UNC path to a centrally located file on a share. The file could be changed once and would effectively change all client connection information at the same time.

More content available in PMR's 55762,227 and 51966,L6Q.

I've already discussed this requirement with Howie B. and Adam S. and was advised to open an RFE to track.

Use Case
Need Windows client to have the option to pull ClearQuest connection information from a file in a centrally managed, shared location every time a login is attempted.
RFE ID 114366
RFE URL
RFE Product Rational ClearQuest
Idea Priority High
  • Guest
    Dec 19, 2017

    A preliminary evaluation of this request indicates that it is consistent with our business strategy. Further evaluation of this RFE is underway.