IBM Sterling Ideas

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

IBM is transforming its request for enhancement (RFE) process. The purpose of the transformation is to provide a more consistent experience for you to submit requests and to enable IBM product owners to respond to your requests more quickly. For more information click here.

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 notifications 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.

Windows Connect:Direct proxy password secure

Wells Fargo is requesting an enhancement to Windows Connect:Direct. Currently when a new user proxy is configured a password has to be entered by the person creating the user proxy. This password, in most cases, is owned by a team other than the NDM administration team with restrictive requirements on its distribution.

We would like a method or tool in Windows Connect:Direct, Sterling Control Center or both that would allow an encrypted account password to be passed to the NDM administrator. That password will then be passed to the NDM sub-system without it being visible to the NDM administrator and the proxy created.
  • Guest
  • Jan 8 2018
  • Future consideration
DeveloperWorks ID DW_ID62067
RTC ID RTC_ID448615
Link to original RFE http://www.ibm.com/developerworks/rfe/execute?use_case=viewRfe&CR_ID=62067
  • Guest commented
    19 Sep, 2018 01:43pm

    The NDM administrator should control what the password is for the local user that is used to setup the remote proxy, not the other way around.  The client just needs to know what ID to include as the snodeid in their process scripts.

By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.